Closed korziee closed 5 years ago
Just so I can move on with the project i'm working on, i've created a real quick and dirty fix. https://github.com/Publift/vue-cli-plugin-browser-extension/commit/876eebe075fc81f9b5f792c5285e2f85b872e122
I think this has been resolved with the use of webpack-extension-reloader
instead of the chrome specific one. Was just released, tonight in 0.16.0
. Any feedback would be greatly appreciated on whether this fixes the issue for you or not.
closing due to inactivity and presumed resolution
EDIT: Clicked enter too early, didn't add a description.
Hi, i'm having an issue with getting the
npm run serve
with the live reload server to work.Whenever I run
npm run serve
i'm consistently getting:The only way to remediate i've been able to remediate this issue was:
webpackConfig.plugins.push(new ChromeExtensionReloader({ entries }))
in thevue-cli-plugin-browser-extension/index.js
file.npm run serve
npm run serve
Some more info:
I've added a
console.trace()
into thevue-cli-plugin-browser-extension/index.js
file, inside theapi.configureWebpack
function and the outputs i'm getting (in order), are the following:Output 1:
Output 2
Let me know if there is anything else I can provide, would really like to get this working.