Announcing @ViteConf 2024! Come get your themed ticket :) viteconf.org/24/tickets/yyx9…

The entire Vite Ecosystem invites you to @ViteConf 💜 viteconf.org/24/ecosystem/vi…

With Vite, we're all Building together, lightning fast! Let's celebrate, learn & grow together at ViteConf 2024! Join us online October 3rd to learn how the best teams are building the next generation of the web with Vite! Grab your free ticket now at viteconf.org🎉

Registrations for ViteConf 2024 are open! 🎉 Get your free ticket and invite others in your communities! This October 3rd & 4th, the Vite Ecosystem gathers for another 24-hour marathon! Let's keep building together. Lightning fast ⚡️ viteconf.org?2024

Very cool stream with @devagrawal09 on @LWJShow showing how he can build a simple metaframework in about an hour with Vinxi. youtube.com/live/2m9ErnaDy6s

In this insightful #frontendnation panel discussion, watch the Vite Core team dive into the world of @vite_js 💜 ✨ @evanyou @patak_dev @bluwyoo @sheremet_va Dominik G ✨ Get insights into the upcoming Vite 6 release, the new Environment API & more! youtu.be/Yt1SBRA4Izw

Introducing "Pass Server Logs" feature on unplugin-turbo-console: It allows you to inspect server logs directly in the browser. Special thanks to Nuxt and @patak_dev 's vite-plugin-terminal for the inspiration. For more detail and usage, check here ⬇️ github.com/unplugin/unplugin…

If you're using @vite_js and @storybookjs, take a look at the RFCs we wrote for a new Storybook+Vitest integration and a @nextjs plugin! Exciting times ahead, but your feedback is super important so please check them out 🧵

DHH promotes a no-build approach in Rails, and many Rubyists are embracing it. I can relate; I still mumble "No, please, not Webpacker" in my sleep. But here's the truth: no-build doesn't scale! Let's explore an alternative approach – using Vite Ruby (and touch on Inertia.js)

📢 @AnalogJS 1.6 is out! ✅ Introduces build-time rendering and syntax highlight for markdown content! Less client-side JS! ✅ Better support for @vitest_dev and @Angular with zone.js⚡️ ✅ Proper support for sourcemaps! Updating to latest 📕 analogjs.org/docs/features/u…

Episode 76 of Svelte Radio is now available! In this episode @kevmodrome is joined by @patak_dev and @evilpingwin. They discuss how Vite evolved into a framework agnostic build tool and what it has planned for the future. svelteradio.com/episodes/sve…

🌀 Introducing Pinorama. Explore logs file generated by Pino Logger — Under development. ✓ 100% Open Source, MIT license ✓ Based on @nodejs , @fastifyjs, #pinojs, @askorama ✓ Uses @reactjs, @tan_stack, @shadcn, @vite_js ✓ Supports piped output! 🔥

Vitest 2.0 is out! - better Browser Mode support (still experimental) - stability improvements (`forks` pool is now the default) - new `blob` reporter to merge reports from different processes - a lot of bug fixes github.com/vitest-dev/vitest…

We've fully migrated from Ava to @vitest_dev in drizzle-orm, drizzle-kit, and all plugin packages. We also fully rewrote the architecture and strategy for testing drizzle-orm with different driver packages, ensuring that all of them had a specific set of tests. This postponed our next set of releases but was a necessary action to ensure we can continue delivering new features faster and with fewer bugs(I hope so) Previously, we had tests like "pg.test.ts" for the "node-postgres" driver, which were written in ava. When adding new drivers, we were just copying everything and changing the way we connected to the database (this was the fastest solution so far to ensure we could move quickly). The codebase for tests was growing by copying everything from one file to another. At some point, when Relational Queries were released, we tried to add new tests using Vitest, so from that time, we had two different libraries for testing. The worst part was that if we needed to add new test cases, we were adding them to the first test file we had (for example, "pg.test.ts" for Postgres), meaning that all other drivers wouldn't have all the needed tests. Copying became harder and harder, so we weren't doing it everywhere. Now, the situation is different: 1. We have everything in Vitest now. 2. Each dialect has a common file with all the tests needed to be run. Each driver has a file explaining how to connect to the database and provides a drizzle DB instance to a common logic to run all tests. So now, each dialect has a common set of tests, and adding new ones will ensure they run for each driver. 3. If some drivers don't have specific features, we have a skipTests() function to skip those tests for specific drivers, like transactions for some HTTP drivers, etc. 4. If some drivers have specific logic, we can define test cases in the driver test files It's on the beta branch now, but I'm releasing it to the latest branch together with the generated column today or tomorrow, so it should be live soon. You can already check the new structure - link in comments ps we skipped a few tests for this release, but I'll check them and add them to the test suites as well

Try rolldown via a click: stackblitz.com/github/rolldo…

Vite-based frameworks such as SvelteKit, Remix, Nuxt, or Astro can now more easily integrate with the Vercel Toolbar. The Toolbar enables you to comment on deployments, toggle feature flags, view draft content from a CMS, and more. vercel.com/changelog/easier-…

🚀 June Releases @vike_js 🧹 48 bug fixes 🎁 6 new features ⚙️ 1 new Vike extension 📜 Improved docs 🧭 Updated roadmap Check out vike.dev/releases/2024-06 to learn more.

Waku, a minimal React framework, v0.21.0-beta.0 is out! You can try it with: `npm create waku@next` waku.gg

I love this "Conventions as a vite plugin" from @markdalgleish 📦 #dotJS

A fast feedback loop is crucial while developing. I just trivially upgraded @linear's codebase from @vitest_dev 1.0.4 to 1.6.0 and found our tests to be 2X faster!⚡️🙏