@vite.dev core team member.https://bsky.app/profile/sapphi.redhttps://bsky.app/profile/sapphi.red/post/3msxcwruum22lI was in the mood to write a blog post, so I wrote one about the mangler. https://green.sapphi.red/blog/how-variable-mangling-works-in-oxc-minifier13 Aug 2026 09:21 +0000at://did:plc:aonb7dtefv5m4v2qf4sljgr2/app.bsky.feed.post/3msxcwruum22lhttps://bsky.app/profile/sapphi.red/post/3mnhso77amk2mI'm excited to join Cloudflare! 😀 I'll continue working on Vite and Rolldown just as before, and Vite 8.1 is already on its way with some interesting new features 👀04 Jun 2026 14:14 +0000at://did:plc:aonb7dtefv5m4v2qf4sljgr2/app.bsky.feed.post/3mnhso77amk2mhttps://bsky.app/profile/sapphi.red/post/3mjwftavvrk2hcrates.io will be using SvelteKit. This means we've come full circle 😄 crates.io → SvelteKit → Vite → Rolldown / Oxc → Rust → crates.io https://blog.rust-lang.org/inside-rust/2026/04/17/crates-io-svelte-public-testing/20 Apr 2026 11:53 +0000at://did:plc:aonb7dtefv5m4v2qf4sljgr2/app.bsky.feed.post/3mjwftavvrk2hhttps://bsky.app/profile/sapphi.red/post/3mgrsn6lqrk2rWondering how Node-compatible runtimes handle vulns in Node. IIRC they use JS code forked from Node, which means they'd have the same vulnerabilities if the vuln exists in the JS side. Does that mean that there's a window where they're vulnerable to 0-day exploits whenever one is discovered?11 Mar 2026 11:43 +0000at://did:plc:aonb7dtefv5m4v2qf4sljgr2/app.bsky.feed.post/3mgrsn6lqrk2rhttps://bsky.app/profile/sapphi.red/post/3mce475lxb22vWorking on a page that you can search vite plugins. I'm planning to allow plugins to add metadata for that page via a field in package.json. I wonder if it's a good idea to use a generic name like `compatiblePackages`. https://registry.vite.dev/guide/extended-metadata14 Jan 2026 03:16 +0000at://did:plc:aonb7dtefv5m4v2qf4sljgr2/app.bsky.feed.post/3mce475lxb22v