khromov.se
🇸🇪 Web developer and obscure trivia enjoyer
🌱 Find me at https://stanislav.garden/
🔵 Starting over on Bluesky
104 posts
747 followers
194 following
Regular Contributor
Active Commenter
comment in response to
post
You can do --target=semver in ncu to lock it to your current semver range! That's what I usually do.
comment in response to
post
Of course! Would love to check it out once finished!
comment in response to
post
Fantastic news!
comment in response to
post
Try Astro, you can name route files to whatever you want and still use Svelte. :)
comment in response to
post
I'm open to it, there's no "final score" currently but one can be calculated. I'm also interested in expanding the test suite because it's pretty basic currently. You are welcome to help out!
comment in response to
post
If you're curious about the code and benchmarks, it's available here:
github.com/khromov/svel...
comment in response to
post
I mean things like the thread below. If you have high amount of visitors you need caching in the http level, but Vercel wants you to send all traffic thorough them. Compare to Astro which have solved this problem on the http level.
www.reddit.com/r/nextjs/com...
comment in response to
post
Why would the devs combine the worst first load performance with frequent trips to the server? Worst of the both worlds, unless it's about something else.
comment in response to
post
Last I checked a hello world in Next.js shipped >300KB of JS. A lot of that must be the RSC runtime because baseline React is much smaller, and Next ships 2-3x more JS for a hello world than comparable frameworks. So perf wise Next is by far the worst framework.
comment in response to
post
My train of thought is, why build such a strange system that conspicuously doesn't work well when self hosted (caching, streaming) and requires frequent round trips to the server. It checks out pretty well with the definition imho.
comment in response to
post
Which other JS frameworks use the RSC paradigm, apart from stuff like Livewire (which is not JS and use it out of necessity?). Do you truly believe React tapped into something nobody else has figured out? Because that sounds unlikely.
comment in response to
post
@fubits.dev If you integrate this into the toolbar then you should be able to use the `<RenderScanObserver />` component directly. Just render/don't render it depending on on/off state.
comment in response to
post
Cool, let me know if something doesn't work well! FYI Right now if you toggle the switch at least once it writes the last saved value to localStorage, this is useful b/c otherwise every full reload will reset it to initial setting. If useful I could add `persist={boolean}` prop to toggle behavior.
comment in response to
post
Nice! If you don't want to deal with the bottom right overlay, I just pushed 1.0.4 where you can use `import { RenderScanObserver } from 'svelte-render-scan';` to just get the highlighting without the icon, or you can pass <RenderScan hideIcon={true} /> prop for the same effect.
comment in response to
post
☀️ What I found in existing projects is that thanks to the fine grained Reactivity in Svelte 5, there is rarely any need to make changes, everything is already optimized out of the box. But still nice to know that it is! :-D
comment in response to
post
Correct. You can also add an Express.js middleware that handles this via custom server:
svelte.dev/docs/kit/ada...
comment in response to
post
The best approach for now might be to tell it to use Svelte 4 if possible, as you still have years of full backwards compatibility.
comment in response to
post
Finally, a spicy opinion one can get behind! 🔥
comment in response to
post
Framework7 is cool but it's an "all in one" package that afaik doesn't work with SvelteKit. If you just want nice components, and you still want to take advantage of SvelteKit, you can use their sister package Konsta UI which has most of the same components. konstaui.com
comment in response to
post
This is HUGE! Amazing!
comment in response to
post
Day 18 — we've upgraded the playground so you can better understand how the compiler transforms your code. We plan to use this tool ourselves to improve the sourcemaps that Svelte generates
🎁 svelte.dev/playground
comment in response to
post
Totally agree. I get most bang for the buck with Claude Projects and a very incremental workflow, asking it to do one small feature or function at a time!
comment in response to
post
It's very good, the generation logic is based on the same code as the site I used in this video! www.youtube.com/watch?v=tprM...