Vinext is now 1.0
what started as the OG slopfork is now just straight up better than running Next.js
npx vinext check && npx vinext init
npx @vinext/cloudflare deploy --warm-cache
@James_Elicx cooked with the traffic-aware cache warming in here
blog.cloudflare.com/vinext-n…
team rolling into July 4th like
"I know not what course others may take; but as for me, give me 100% test coverage of the Next.js test suite or give me death!"
vinext 1.0 beta is here. just crossed 90%. 100% next.
give your Next.js app independence from the the Stamp Act of 1765:
npx vinext init
npx skills add cloudflare/vinext
prompt: migrate this project to vinext
Introducing "cf", an agentic CLI for the entire Cloudflare API.
You can do nearly anything. Even buying a domain is incredibly simple from the CLI.
Don't know what command you need? Run `cf cli search "look at messages stuck in my queue"` and it will return a list of relevant commands.
blog.cloudflare.com/cloudfla…
Vite+ 1.0 is out:
* Fast tools
* No config
* Less time and fewer tokens wasted
Almost 2m downloads per week too, what are you waiting for?
voidzero.dev/posts/announcin…
We're also working on a significant improvement to chunking.
In the next version of Rolldown, we'll ship an experimental feature, inlineCommonChunks, which can reduce the number of small shared chunks.
github.com/rolldown/rolldown…
Hey, I joined the VoidZero team!
I'm still at Cloudflare — VoidZero is part of Cloudflare! — and will continue as a Developer Advocate.
I'll also work on synergy between Hono and VoidZero products like Vite, Vite+, Oxc, and Void, and advocate for them!
Vite+ v1.0.0-rc.1 is out.
- Task cache settings like `env`, `input`, and `output` now go under `cache`.
- `vp lint` and `vp fmt` in a package directory now use the same config as your editor.
Run `vp upgrade`, then `vp migrate` to move your task settings.
github.com/voidzero-dev/vite…
Quick update on Vite's bundled dev mode (aka full-bundle mode, powered by Rolldown)
The whole Vite playground suite now runs under bundled dev, and ~74% of the tests that had gaps now pass.
(1/5)🧵
Vite+ v1.0.0-rc.0 is out.
vp test uses Vitest 5. vp migrate guides Vitest 4 projects through the upgrade. Standalone installers and vp upgrade verify npm provenance.
Upgrade with: vp upgrade
github.com/voidzero-dev/vite…
We will ship the official Vite+ v1.0.0 release soon.
It's been a while...
Introducing Devframe v1.0 🚀
The framework for building DevTools that can run everywhere, for any meta-framework, for both humans and agents.
Check out the announcement post and join our Discord 👇
devfra.me/posts/pluggable-ex…
Thoughts on oj:
1. It is an impressive project and solves Lovable's problem well. Great work!
2. It is not an entire rewrite of Vite. It is built on the same foundation of Rolldown / Oxc maintained by the VoidZero team, with only the dev server parts rewritten in Rust.
3. Hyper-customization pays off, with different trade-offs. oj optimizes by only needing to support certain types of apps, and aggressively rustifying dependencies in that happy path. The current level of compatibility is impressive, but it does not cover the full range of Vite usage. Vite operates under a different set of constraints - more frameworks, app variations, and downstream dependents to support, and we intentionally leave some dependencies external so users can upgrade them individually.
4. The benchmark in the blog post is somewhat misleading. It notes the Vite cold start time includes the significant overhead of vite-plugin-checker, which oj does not run. In the benchmark shown in the repo (github.com/lovablelabs/oj/bl…), latest Vite with full bundle mode is closely on par with oj on cold start metrics. That said, oj uses significantly less memory, and that is surely something we should aim to improve in Vite itself.
5. Open source dynamics is changing. With the cost of re-implementation collapsing due to AI, we will likely continue to see more "tailored projections" of open source dependencies that are re-implemented under different constraints to optimize for specific use cases (TanStack's redact comes to mind). A possible future is instead of maintainers being overwhelmed by thousands of slop PRs, everyone just maintains their own slop fork. I am honestly not sure if that's good or not, but I think it's quite likely what will happen in a few years.
We rewrote the vite dev server in rust.
By removing Node.js, we achieved 4x better memory usage and cold starts is 2x faster.
This has resulted in our sandboxes acquisition time to go from 14s to 3s (4.6x improvement).
When i say we, i mean @raphamorims
Vite+ v0.3.2 is out!
Set package-manager versions independently with `vp env use`. Build custom Oxlint rules with the new plugin APIs. Includes Vite 8.3 and migration and installer fixes.
Upgrade: `vp upgrade`
github.com/voidzero-dev/vite…
Excited to share that Oxc and Rolldown now support property mangling!
It shortens internal property names to reduce bundle size. This was a missing piece for some projects moving to Vite 8, and it’s finally here.
Try it in the demo ↓
repl.rolldown.rs/#eNp9U8Fu2z…