Jack Steam

> Is manifest V2 going to be supported with new currently beta version of the plugin ? The Chrome Web Store no longer accepts new MV2 extensions, and Chrome won't...

> On Firefox's end, the browser doesn't support MV3 yet, so I'm curious to see whether the MV3 support will be added before Google officially terminates support for MV2 @avi12...

@DetachHead Good idea, thanks!

@DetachHead @mnoorenberghe It seems that this issue is mostly about type errors in the Vite config. Since the config is browser-agnostic, perhaps we should fix the library manifest type and...

We need better support for unbundled scripts. I like the idea of putting them in `public`, seems like a reasonable approach is to check if a script in the manifest...

@GoodSimonVM Thanks for the great repro! I'll put this on the roadmap, until then PR's are welcome 👍 Since things work as expected without custom `root` values, I'm considering this...

> Unable to load "/@react-refresh" from server @keyding RPCE auto-detects if the Vite React plugin is installed and applies the React Refresh preamble to content scripts. If the plugin isn't...

> The css file is not applied. Only `RPCE@>=4.0.1-18` fully supports content scripts in development.

> things are working with build because it doesn’t follow the same path as when running dev True! build and dev are very different. `contentScripts.preambleCode` is used for HMR (which...

> neither the `rm` nor the `preambleCode` option fully fixes the issue @mismith If you're still looking for a fix, could you create an issue? 🙏 I don't want your...