Joaquín Sánchez

🚀 The PWA update train continues! @vite-pwa/vitepress v2.0.0 is officially out. Bringing all the latest PWA goodness and core improvements straight to your VitePress docs. Time to upgrade! ⚡️🛠️ github.com/vite-pwa/vit...

@cyberalien.dev I'm testing this new iconify custom loader, I will try to send a PR to iconify utils this weekend: github.com/unplugin/unp...

I created my ViteConf 2026 mission credential. Create yours! viteconf.org/tickets/t/Zk...

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

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

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

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 🙏

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

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 ❤️.

And here the build output: #webpack #workbox

🐐 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.

💥 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.

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

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

Just hacking ESM service worker support works with classic:

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

👀 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...

We're working on vite-plugin-pwa v2 version: - 🦾 workbox fork: from 340+ to just 20 dependencies ( @e18e.dev ) 🤯 - ⚡ @vite.dev 8 + Environment API support (v1 works with Vite 8) - 🔌 pwa plugin becomes modular, we don't need to hack integrations anymore (ala npmx.dev/package/serw... )

👀 I have no idea what's going on, but 2.5 million downloads per week is insane🎉🥳 🤗: npmx.dev/package/vite...

Moving packages to a monorepo is great... until you hit the GitHub Releases page. 🫠 ​Come on @github, it's 2026! We need real workspace support: 🏷️ Mark MULTIPLE packages as latest 🔄 Better sorting for tags/releases (save us from the alphanumeric inferno 🔥) ​#monorepos #github

You can now break down import and transform times in @vitest.dev! This works in the Vitest UI, the terminal and also via the VS Code extension. Time to find out why tests are taking longer than expected! 👀 More in the docs vitest.dev/config/exper...

Published new major version of Iconify Tools. Changes: - Dropped CommonJS support - Massively reduced number of dependencies - New small XML parser Migration should be seamless, almost everything is the same. iconify.design/news/2025.ht...