You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My org is currently looking to migrate to a Framework to facilitate development of our Chrome Extension.
Currently, our top 2 picks are this library and Plasmo.
Our current tech stack is React + CSS Modules + SCSS.
To us, the big selling point of this library is that HMR works for Content Scripts.
However, if HMR doesn't work for styling changes and we're forced to refresh the page anyways, it disrupts development workflow too much and defeats the purpose of having HMR at all.
Without Content Scripts HMR, Plasmo appears to be the more attractive option.
Personally, I hope this is fixed or addressed soon before a decision is made in my org because after playing around with this library, I'd say I prefer it over Plasmo.
Basically:
CSS modules breaks HMR in content-scripts. This does not happen in Popups.
Build tool
Vite
Where do you see the problem?
Describe the bug
My org is currently looking to migrate to a Framework to facilitate development of our Chrome Extension.
Currently, our top 2 picks are this library and Plasmo.
Our current tech stack is React + CSS Modules + SCSS.
To us, the big selling point of this library is that HMR works for Content Scripts.
However, if HMR doesn't work for styling changes and we're forced to refresh the page anyways, it disrupts development workflow too much and defeats the purpose of having HMR at all.
Without Content Scripts HMR, Plasmo appears to be the more attractive option.
Personally, I hope this is fixed or addressed soon before a decision is made in my org because after playing around with this library, I'd say I prefer it over Plasmo.
Basically:
CSS modules breaks HMR in content-scripts. This does not happen in Popups.
Reproduction
https://github.com/Noir-Lime/crx-bug
Reproduction steps are in Readme.
Logs
No response
System Info
Severity
blocking all usage of RPCE
The text was updated successfully, but these errors were encountered: