iiinova — where your digital self keeps evolving

Joaquín Sánchez @userquin.bsky.social · 01/10/2026

Nice, you should review color contrast, that orange and white bg color on light theme (~2.7)...

Joaquín Sánchez @userquin.bsky.social · 18/07/2026

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

Vite PWA Inspector showing PWA web manifest including icons (like chrome devtools) integrated with Vite devtools.

1102

Joaquín Sánchez @userquin.bsky.social · 23/06/2026

wowow, cannot wait your test on iOS emulator

151

Joaquín Sánchez @userquin.bsky.social · 23/06/2026

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

streamable.com

Watch Vite App — Mozilla Firefox Navegación privada 2026-06-23 14-48-06 | Streamable

Watch "Vite App — Mozilla Firefox Navegación privada 2026-06-23 14-48-06" on Streamable.

1122

Joaquín Sánchez @userquin.bsky.social · 17/06/2026

What are you doing with your laptop on? Close it and go eat some Galician-style octopus, mejillones or percebes (beware, percebes quite expensive).

120

Joaquín Sánchez @userquin.bsky.social · 14/06/2026

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

webpack CJS configuration using require to load workbox-build ESM plugin to build the service worker

061

Joaquín Sánchez @userquin.bsky.social · 14/06/2026

Como le da a los churros Daniel 🤤

130

Reposted by Joaquín Sánchez

Jan-Niklas Wortmann @wordman.dev · 11/06/2026

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

plugins.jetbrains.com

Slidev - IntelliJ IDEs Plugin | Marketplace

Integrated support for Slidev presentations. Auto-detects slides.md Slidev projects in your workspace Starts, adopts, and stops the Slidev dev server (configurable dev...

1132

Reposted by Joaquín Sánchez

patak @patak.cat · 08/06/2026

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 🙏

4658

Reposted by Joaquín Sánchez

Matthew Ary 🇺🇦 @matthewary.com · 06/06/2026

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.

2103

Joaquín Sánchez @userquin.bsky.social · 05/06/2026

finally, is this v3 or still v2?

120

Joaquín Sánchez @userquin.bsky.social · 26/05/2026

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

rsbuild app build output using vite-pwa workbox via rspack plugin

061

Joaquín Sánchez @userquin.bsky.social · 24/05/2026

🐐 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

an screenshot with 3 parts using webpack plugin on a webpack app v5 using type module (.mjs config file) using dual service worker build: on the left generated output with workbox runtime chunk code split; on the center some proces.env variables; and on the right, the classic service worker chunk showing those env variables, only exposing those starting with VITE_ and PUBLIC_

072

Joaquín Sánchez @userquin.bsky.social · 23/05/2026

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.

Picture at MadVue: Juan Nuñez, Alex Jover, Eduardo, Daniel and me

1190

Reposted by Joaquín Sánchez

daniel wraith @danielroe.dev · 22/05/2026

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

1116228

Reposted by Joaquín Sánchez

Yann Braga @yannbf.bsky.social · 20/05/2026

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

3639

Joaquín Sánchez @userquin.bsky.social · 20/05/2026

Proudly developing in Sveltnux 😱🤪

020

Reposted by Joaquín Sánchez

Kevin Deng @sxzz.dev · 20/05/2026

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.

github.com

GitHub - sxzz/actionspack: Lockfile-first GitHub Actions workflow packer

Lockfile-first GitHub Actions workflow packer. Contribute to sxzz/actionspack development by creating an account on GitHub.

3114

Joaquín Sánchez @userquin.bsky.social · 20/05/2026

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

141

Joaquín Sánchez @userquin.bsky.social · 17/05/2026

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

service worker using multiple custom chunks

service worker dependency using custom chunk

141

Joaquín Sánchez @userquin.bsky.social · 14/05/2026

We've decimated the workbox-build footprint: 📦 From 350+ dependencies down to ~30. 🚀 ESM-first, Vite 8 ready, and powered by Node 22+. #PWA #ViteJS #Rolldown #WebDev #BuildTools

070

Joaquín Sánchez @userquin.bsky.social · 14/05/2026

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! 🤯

screenshot with the code for generate service worker strategy using import.meta.env inside a runtimeConfig handler and the classic-sw generated with the import.meta.env data inside the registerRoute callback

screenshot with the code for build service worker strategy using import.meta.env.DEV inside an if statement and the classic-sw generated with the if using import.meta.env.DEV removed

110

Joaquín Sánchez @userquin.bsky.social · 13/05/2026

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

workbox-build fork dependencies adding back support from Vite 3.1 to Vite 8

050

Joaquín Sánchez @userquin.bsky.social · 07/05/2026

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

Vite 8 building 2 classic and module service workers in parallel with workbox chunk and sourcemap (35 milisenconds and 28 milesconds respectivelly)

061

Joaquín Sánchez @userquin.bsky.social · 03/05/2026

Less weight, more control, 100% Type-Safe. 🛠️💎 #WebDev @rolldown.rs #BuildTooling

090

Joaquín Sánchez @userquin.bsky.social · 03/05/2026

How did we do it? Our new Workbox fork is pure muscle: 📦 Tree-shakeable: Even when using the "@vite-pwa/workbox-swkit" barrel. 🛡️ IIFE Isolation: Runtime is auto-wrapped to prevent global scope collisions when using classic service worker. 🪓 Ultra-lean: From 346 dependencies down to just 14.

150

Joaquín Sánchez @userquin.bsky.social · 03/05/2026

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

1214

Joaquín Sánchez @userquin.bsky.social · 03/05/2026

Just hacking ESM service worker support works with classic:

forcing classic service worker using supportsESM at registerSW options

using classic service worker with firefox

using classic service worker with chrome

040

Joaquín Sánchez @userquin.bsky.social · 03/05/2026

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

Vite VanillaJS example with the main.js entry point with dual service worker (classic and module) and service worker ESM detector.

Vite VanillaJS project with service worker type module at chrome

Vite VanillaJS project with service worker type module at firefox

071

Joaquín Sánchez @userquin.bsky.social · 01/05/2026

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

Vite PWA workbox-build fork preparing classic SW build with a warning when using @vite-pwa/worbox-swkit barrel export:
[Vite PWA] Oh, you sweet summer child...
You're using the '@vite-pwa/workbox-swkit' barrel export in IIFE format.
Your users will need a NASA-grade connection to download this beast.
Switch to subpackage imports (e.g., '@vite-pwa/workbox-swkit/core') to save some souls.

150

Joaquín Sánchez @userquin.bsky.social · 27/04/2026

invitation sent to my monorepo, check this post bsky.app/profile/user...

120

Joaquín Sánchez @userquin.bsky.social · 27/04/2026

The packages/core folder is the current vite-plugin-pwa, I need to add the node/vite stuff using my PR for vite environment api. I can give access to anyone at google, just reply to this message with the github username. #pwa

011

Joaquín Sánchez @userquin.bsky.social · 27/04/2026

The examples/workbox-cli/generate.ts module is working fine when using `swType: 'classic'` or `swType: 'module'` , but not with `swType: 'classic-and-module'`. You can find the esm-sw-detector module at packages/core/src/client/esm-sw-detector.ts.

110

Joaquín Sánchez @userquin.bsky.social · 27/04/2026

Finally using tsdown instead @rolldown.rs , the main issue: Rolldown removed AMD and so we cannot generate the sw and workbox chunk. I've added `@babel/core` and 2 babel plugins (amd and dynamic imports) to do the build. @viteconf.org pwa plugin with same problem (I'll export some utils)

120

Joaquín Sánchez @userquin.bsky.social · 27/04/2026

I'm adding dual classic and module builds, I need to fix a problem with the logic for dual generation at generateSW. Check examples/workbox-cli/generate.ts.

100

Joaquín Sánchez @userquin.bsky.social · 27/04/2026

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 🙏

210