@vitest.dev just surpassed Jest in npm weekly downloads 📈
npmx.dev/compare?pack...
Posts by Antoine
First peek at Svelte 5 + NativeScript 🚀
Big thanks to @paolo.ricciuti.me, @svelte.dev, @syntax.fm and @mainmatter.com
This monthly recap is SO USEFUL, so cool to see these tools getting better and better!
March was PACKED for the Vite ecosystem. 👀
Vite Plus, Vite 8 with Rolldown, Vitest test tags, Oxlint JS plugins, and much more.
Full recap in the video!
www.youtube.com/watch?v=pyiA...
There is also the fact that we can already see the first signs of v5 in the issue tracker, v4 looks feature complete already
Also, what are the % of people still in v3?
I say release v4! People likely won’t care or will be relieved
My take is: after that big of a number of betas and so much time, the "weight" of the risks of a beta version fades out more and more
The largest factor for considering v4 as stable already is the fact that the install script installs the v4 BETA by default instead of v3 like you’d expect
Navbar of Vitest's "learn" section in the docs, showing menu items like "Using Matchers" or "Writing Tests with AI"
Want to start writing tests but no idea how to get started?
The @vitest.dev docs now have a Learn section that covers evergreen concepts (matchers, tests, dealing with async code, mocks, ...) and also current topics like writing good tests with AI!
Time to get started 🎉
I dearly miss my sweet sweet $derived.by
How did we live like that before
How do you feel the framework change right now? 👀
🚀 We just shipped v.0.231!
Git graph is finally here: Open it from the git panel or the command palette (git graph: open).
What were you using before? Any thoughts?
Write down CSS and JS full size but replacing every S by the Svelte logo 😎
😂😂😂
Idk what website you’re linking to but I personally objectively think its og image is absolutely gorgeous and the site rocks
Props to its creator!
Nice SvelteKit release btw! (😂😂)
"Always has been" meme but the opposite, about React
Yeah I wasn’t sure if it fit in your "via JS" category
What I tend to do is using `Pathname` directly instead of string in my NavItem type
`as const` fixes the issue but doesn’t provide autocomplete and as such doesn’t prevent bad paths (as early)
No as const, no cast, intellisense, and early errors!
what the freaking f**k is this absolute madness
one can't love svelte enough i swear
And they say you can't do everything with Svelte...dunno it seems pretty capable U_U
I'm gonna replace all my git usage with this. lol
Personally I use $lib/{assets,components,server}, the rest is at the root of $lib
As for inside components, shadcn stuff in its subdirectories, the rest directly in here
I really *hate* when new stuff is released without even _mentioning_ that it’s React-only
If your thing doesn’t even provide a vanilla JS impl, call it a React thing and not just a thing
I get that React is the default, but it’s not alone, far from it
Btw it might be a "false alarm" as it’s just an old package that haven’t had releases for over a year now
My detection algorithm flags it as new cause its recent update is the oldest release I can get from the api so it doesn’t know it existed for longer…
Haha let’s call it an intentional teaser for next week 👀😂
Custom renderers, community add-ons, such as good episode thank you!
I noticed on your svelte changelog that you skipped over a new "typescript-svelte-plugin", was it intentional like for sv-utils or something you forgot to talk about 👀👀 ?
Yeah yeah it works really well
It’s just not an $effect killer similar to the $state callback, just a nice controlled $effect alternative!
(Watch runs an $effect under the hood though so I wasn’t quite right 😅)
Damn yeah this would be such an $effect killer it’d be crazy
Have to stick with runed’s `watch` for now!
Update: working!
(Not installed locally as it has too many deps + it's fine enough to run it manually from time to time)
github.com/WarningImHac...
It’s absolutely CRUCIAL that this lands in shiki-magic-move’s readme!
What do you think about it @antfu.me?