Closed hughsaffar closed 5 years ago
I think this is a known gotcha from some of the codesplitting that was fixed in #16. I'm going to cut a release tonight, and upon an update, should fix your production building issues.
I think there are a few breaking changes, so you might, commit your changes, rescaffold your application and fix the diffs.
Just to follow up, is this still an issue for you?
I'm having a related problem with assets imported with ~@/assets/etc
. The path is translated to ../assets/
but should be ../../assets/etc
because the bundle is in /popup/popup.js
instead of /popup.js
.
closing due to inactivity and presumed resolution
The extension I created using this plugin is working fine in the development mode, however, when I do
yarn build
and load up the unpacked into the Chrome extensions, it does not work anymore! I get no error anywhere, but I can not see any of mybackground.js
cosole.log
s! Any idea where should I start to dig in order to fix it?