Wispr Flow: Dictation That Works EverywhereStop typing. Start speaking. 4x faster.
Promoted
Extro
Next.js for Chrome extensions
14 followers
Next.js for Chrome extensions
14 followers
Build Chrome extensions with the same developer experience you'd expect from a modern web framework. File-based extension surfaces, automatic Manifest V3 generation, React Fast Refresh, routing, TypeScript, and a one-command setup.
Tried the one-command setup and had a working extension running in under a minute, which is wild compared to the usual copy-paste boilerplate. The file-based surfaces approach actually makes the manifest feel like it disappears into the background where it belongs.
@mehmetvmqg Really appreciate you giving it a try! That was exactly the goal. I wanted the manifest to fade into the background so you can focus on building your extension instead of wiring everything together.
Hot reload across extension contexts would be huge, like updating the service worker and popup without losing state or needing to reopen the chrome://extensions page. Most painful part of extension dev right now.
@idemyfzj That's the direction I'm headed at! Really appreciate for checking it out ❤️
Manifest V3 setup is usually the worst part and this just handled it. Hot reload actually works on extension pages too which caught me off guard in a good way.
@sasaralwzc3 Thanks for checking it out! The goal is to let developers spend less time thinking about Manifest V3 and extension wiring, and more time building their extension. Ideally, building a Chrome extension should feel as straightforward as building a Next.js app.
honestly the file-based extension surfaces approach is pretty clever, makes manifest v3 setup feel way less painful than it usually is