Philippe Serhal

@philippeserhal.com

💼 Staff Engineer @netlify.com, frameworks, build system, CLI 🔨 Open source @npmx.dev, forges, gatsby. Vite team advisor.

In a "The cobbler’s children have no shoes" situation, the (12 year old!) @netlify.com app codebase is still on webpack. In an effort to improve DX/AX by speeding up builds and dev and so on, I've been slowly trudging through a migration to @vite.dev. 4 more small PRs to go, then The Big One. 🤞

Truncated screenshot of a GitHub pull request showing:

PR 1: refactor: use Vite-compatible svg imports #26988
PR 2: build: fix invalid import patterns #26999
PR 3: refactor: use browser base 64 API instead of Node.js polyfill #27106
PR 4: build(storybook): switch from Webpack to Vite #27110
PR 5: build(storybook): upgrade to Storybook 10 #27212
PR 6: build: upgrade to Vite 8 (Rust-powered Rolldown!) #27202
PR 7: fix: remove or fix invalid CSS caught by LightningCSS #27204
PR 8: build: opt Vite Storybook back into LightningCSS #27205
PR 9: build: generate _headers outside webpack #27618
PR 10: build: fix favicons script #27659
PR 11: build: link committed favicons instead of re-generating them #27662
PR 12: build: remove no-op ResourceHintWebpackPlugin #27761
PR 13: build: decouple Bugsnag sourcemap upload from Webpack #27939

Nitro v3 RC is out with a stable API. 5× smaller install size, runtime mode, Vitest support, and so much more ⚡️

Daniel Roe, the creator of Nuxt, and the NPMX team released a JS client that can connect to any Git forge and they were gracious enough to include Pushin! Thanks to then and their valuable feedback, Pushin’s API is now much better. Thank you, NPMX team! ❤️

daniel r(ooooooh) at jsconf mx 🇲🇽@danielroe.dev · 2w ago

🙋‍♂️ what if one client worked on every forge? 𝔣𝔬𝔯𝔤𝔢𝔰 is a new TypeScript library for issues, PRs, notifications, checks and webhooks across 12 forges ✨ forges.link

🚀 Check out what I've been spending my evenings working on with some OSS friends! 👀 It's so exhaustive and ambitious already. 💭 What will you build on top of this? Does this give you ideas? What didn't seem possible before that may now be in reach?

daniel r(ooooooh) at jsconf mx 🇲🇽@danielroe.dev · 2w ago

🙋‍♂️ what if one client worked on every forge? 𝔣𝔬𝔯𝔤𝔢𝔰 is a new TypeScript library for issues, PRs, notifications, checks and webhooks across 12 forges ✨ forges.link

Since last ViteConf, @pi0.io has spent his time on @nitro.build v3: H3 rewritten on web standards, a compiled router, route rules in core. Wondering what is left before stable? Tune in for his talk "Nitro v3: the road to stable" @viteconf.org 2026, TODAY 2pm UTC. Free and online.

You can't stop maintainers getting phished. But what you can is stopping bad release reaching your lockfile! Set a minimum publish age, approve install scripts per version, let pnpm reject trust downgrades. @43081j.com in "Securing the JavaScript Ecosystem" 🔒️ @viteconf.org, today, 14:00 UTC