Integrating Vite PWA Inspector with @vite.dev devtools, the inspector can run also as a seperated middleware (ala vite-plugin-inspect or UnoCSS inspector). @tomayac.com #PWA

wowow, cannot wait your test on iOS emulator

Vjacheslav Trushkin@cyberalien.dev · last mo.

Nice! Tested in Safari, demo works without issues.

Fixed color constrast (wcag-aa) adding some changes to the button layout: streamable.com/ed5kjm

Joaquín Sánchez@userquin.bsky.social · last mo.

This is amazing, I'm speechless, this is the new `@vite-pwa/unplugin-pwa` UI Service Worker UI Switcher when enabling dev options, just a few HMR @vite.dev plugins and some client logic. We need to add support for @webpack.bsky.social and @rspack.dev , stay tuned. streamable.com/ue4qx1 #pwa

This is amazing, I'm speechless, this is the new `@vite-pwa/unplugin-pwa` UI Service Worker UI Switcher when enabling dev options, just a few HMR @vite.dev plugins and some client logic. We need to add support for @webpack.bsky.social and @rspack.dev , stay tuned. streamable.com/ue4qx1 #pwa

Babel 8! After all these years! What a surprise! babeljs.io/blog/2026/06...

The workbox fork at Vite PWA Org. is ESM only (all its packages). Here a CJS example with webpack 5 using require(<esm>) to load the workbox-build webpack plugin (node ^22.14.0, and @rolldown.rs ^1.0.0.0-0 required for the build): #webpack #pwa

patak@patak.cat · 2mo ago

Massive jump on ESM-only adoption! The difference with previous years growth shows how important @joyeecheung.bsky.social pragmatic require(esm) approach is going to be for the npm ecosystem (thanks a ton, once more!). If you are a maintainer, drop your dual setup and move to ESM-only, too 🙏

My @sli.dev plugin for @jetbrains.com IDEs is live (alpha). Auto-detects your slides.md, manages the dev server, completion in the editor, live preview, navigation to imported slides, syntax highlight for magic-move, quick docs for front matter... plugins.jetbrains.com/plugin/32201...

Massive jump on ESM-only adoption! The difference with previous years growth shows how important @joyeecheung.bsky.social pragmatic require(esm) approach is going to be for the npm ecosystem (thanks a ton, once more!). If you are a maintainer, drop your dual setup and move to ESM-only, too 🙏

Titus 🇵🇸@wooorm.com · 2mo ago

Hello friends and welcome to another “how’s ESM vs CJS doing?!” A big win this time, at a year of `require(esm)` available! 38.0% of the popular npm packages now have ESM, up from 33.4% half a year ago. ESM-only is up from 12.6% to 16.0%. Particularly this non-dual, “vanilla” growth is very big!

Do I know anyone that works at @discord.com ?

Matthew Ary 🇺🇦@matthewary.com · 2mo ago

The Vuetify project has experienced a major hack of it's Discord server, which has served as the glue for a thriving OSS community for a decade. The scope and scale of the damage that has been done is hard to describe.

The Vuetify project has experienced a major hack of it's Discord server, which has served as the glue for a thriving OSS community for a decade. The scope and scale of the damage that has been done is hard to describe.

🐐 Here @rspack.dev app building the service worker via @rolldown.rs with the workbox fork at @vite.dev PWA. Thank to Néstor (ZEPH) for the webpack/rsbuild examples and plugins review ❤️.

Joaquín Sánchez@userquin.bsky.social · 2mo ago

🐐 Building dual service worker with webpack v5 via @rolldown.rs : - workbox runtime code splitting - import.meta.env using generateSW strategy (only ESM version) - env vars working: added those starting with VITE_ and PUBLIC_ prefix - SW build manifest (ala @vite.dev manifest) - tree shakeable #pwa

And here the build output: #webpack #workbox

Joaquín Sánchez@userquin.bsky.social · 2mo ago

🐐 Building dual service worker with webpack v5 via @rolldown.rs : - workbox runtime code splitting - import.meta.env using generateSW strategy (only ESM version) - env vars working: added those starting with VITE_ and PUBLIC_ prefix - SW build manifest (ala @vite.dev manifest) - tree shakeable #pwa

🐐 Building dual service worker with webpack v5 via @rolldown.rs : - workbox runtime code splitting - import.meta.env using generateSW strategy (only ESM version) - env vars working: added those starting with VITE_ and PUBLIC_ prefix - SW build manifest (ala @vite.dev manifest) - tree shakeable #pwa

Daniel is amazing! After his talk at MadVue, he sat next to me and I watched him testing the new workflow live. I finally met some friends in person yesterday at MadVue, great day.

danielroe@danielroe.dev · 3mo ago

💥 just released a github action: `uppt` it aims to be a very simple, secure release workflow for maintainers that adheres to best security practices ⚪ trusted, staged publishing on npmjs.com ⚪ github environment protection ⚪ generated release PR + changelog ⚪ automatic release + publish on merge ✨

💥 just released a github action: `uppt` it aims to be a very simple, secure release workflow for maintainers that adheres to best security practices ⚪ trusted, staged publishing on npmjs.com ⚪ github environment protection ⚪ generated release PR + changelog ⚪ automatic release + publish on merge ✨

What do you think of a dev tool that helps you inspect components in your live app and then save that snapshot as a story in Storybook? 🤔 Backed by the incredible Vite devtools of course @antfu.me <3

Recent supply-chain poisoning incidents made one thing obvious: CI should not blindly trust floating @main refs. actionspack brings a pnpm-like lockfile to GitHub Actions: author in .github/workflows/src, inline safe workflows/actions, pin the rest to SHAs, and review updates with git diff.

In case you need to enforce sha pinning, take a look at this package (la Anthony Fu's taze).

Andrey Sitnik@en.sitnik.es · 5mo ago

Another GitHub Action hack where old versions were swapped to infect CI. socket.dev/blog/trivy-u... It’s another example of why you should pin actions in your workflows by commit SHA, not by version tags. For JS projects, use actions-up: github.com/azat-io/acti... For everything else: pinact.

Added support for custom chunks fr both @vite.dev or @rolldown.rs , not just workbox; inlineWorkboxRuntime is just a shortcut for custom chunks: #pwa

Looks like we've got @rolldown.rs working natively with: ✅ envDir & envPrefix support. ✅ Full import.meta.env injection. ✅ Aggressive Tree-shaking (Dead Code Elimination). The best part? This isn't just for manual scripts. We can now use import.meta.env even with the generateSW strategy! 🤯

Joaquín Sánchez@userquin.bsky.social · 3mo ago

We're adding legacy support for Vite < 8 via Rolldown, but we need to add the following features to Rolldown manually: - envDir and enfPrefix - import.meta.env

We're adding legacy support for Vite < 8 via Rolldown, but we need to add the following features to Rolldown manually: - envDir and enfPrefix - import.meta.env

Joaquín Sánchez@userquin.bsky.social · 3mo ago

PWA Plugin v2 will be a necessary "clean break": Vite 8 + Rolldown required. ⚡️ 🚀 Native "Dual Service Worker" support: we serve native ESM to modern browsers and automatically fallback to Classic for the rest. The best of both worlds with zero config! ✅🚀 @vite.dev #PWA

@vite.dev 8 build almost done (it is fast running 2 builds in parallel), working on @rolldown.rs build:

Joaquín Sánchez@userquin.bsky.social · 3mo ago

PWA Plugin v2 will be a necessary "clean break": Vite 8 + Rolldown required. ⚡️ 🚀 Native "Dual Service Worker" support: we serve native ESM to modern browsers and automatically fallback to Classic for the rest. The best of both worlds with zero config! ✅🚀 @vite.dev #PWA

PWA Plugin v2 will be a necessary "clean break": Vite 8 + Rolldown required. ⚡️ 🚀 Native "Dual Service Worker" support: we serve native ESM to modern browsers and automatically fallback to Classic for the rest. The best of both worlds with zero config! ✅🚀 @vite.dev #PWA

Just hacking ESM service worker support works with classic:

Joaquín Sánchez@userquin.bsky.social · 3mo ago

After reviewing the custom build strategy at workbox-build fork, I have dual SW working at @vite.dev VanillaJS example with a custom pwa plugin 🎉: @tomayac.com @jeff.posnick.org #pwa

After reviewing the custom build strategy at workbox-build fork, I have dual SW working at @vite.dev VanillaJS example with a custom pwa plugin 🎉: @tomayac.com @jeff.posnick.org #pwa

😎😁 Adding some vitest test at workbox (build) fork. #pwa

Hey @tomayac.com sent an invitation to my private monorepo, you can find workbox at packages/workbox folder. The monorepo created to have all the packages there, but will be moved to the corresponding GH repo at Vite PWA Org. @ducanh2912.bsky.social if you want access ping me 🙏

👀 What's this? 😁 @jeff.posnick.org @tomayac.com @ducanh2912.bsky.social we need to talk ;) #pwa

Awesome projects, great teams ✌️

@vitest.dev now has a new `--experimental.preParse` flag to avoid running all test files when you apply filters. For example, if you have `.only` tests or use `-t` or `--tags-filters` Vitest will now only run matching test files. Try it now! vitest.dev/config/exper...