Jack Steam
Jack Steam
For now, I suggest downgrading as @saxoncameron describes. CRXJS support for Vite 3 will land in or directly after #427. The file writer rewrite will fix this resolution problem at...
@emircanerkul Could you link to a GitHub repo with a minimum reproduction? Thanks 🙏
@emircanerkul Awesome, thanks!
> Sourcemap is likely to be incorrect: a plugin (crx:manifest) was used to transform files, but didn't generate a sourcemap for the transformation. @evanb2 I think this warning is likely...
React and Vue required special handling. I'd need to look into how preact HMR is implemented.
Eventually, this will be something to fix in userland, but we need to get the plugin API stable.
@DetachHead We're not supporting `vite build --watch` right now. The development build is highly specialized for the Vite development server, so it's kind of a big feature. What's your use...
`@crxjs/[email protected]` features a complete rewrite of the code that caused this bug. I haven't tested it extensively, but it may work: https://www.npmjs.com/package/@crxjs/vite-plugin/v/2.0.0-beta.1
@Chersquwn Thanks for reporting this discrepancy between the Chrome developer docs and CRXJS! I downloaded and tested the sample extension with `default_icon` as a string and it does work in...
> Because of the content loader and the async stuff Are you talking about this? https://github.com/crxjs/chrome-extension-tools/blob/a9baf3b3fb5887f8f41c203f16398e9896583309/packages/vite-plugin/src/client/iife/content-dev-loader.ts#L4-L10 Content scripts are tricky b/c they load from the file system and don't support...