Open robertdavid010 opened 3 years ago
For those who came here thinking this was the reason why none of the extension pages were being loaded on a clean install, this error does not cause that.
Instead, for me I created the project using Vue3, while the scaffolding code seems to be using the Vue2 syntax (correct me if I'm wrong). What I did to fix this was to replace each main.js
file's code from
import Vue from 'vue'
import App from './App.vue'
/* eslint-disable no-new */
new Vue({
el: '#app',
render: h => h(App)
})
to
import { createApp } from 'vue'
import App from './App.vue'
const app = createApp(App);
app.mount("#app")
This allowed the content pages to render (for me). Hope this helps.
Describe the bug The console for both the background process, the content script (when used), and the popup all show a source map error:
Related issue (no reason for closing, or solution given): https://github.com/adambullmer/vue-cli-plugin-browser-extension/issues/78
Potentially related issue: https://github.com/adambullmer/vue-cli-plugin-browser-extension/issues/98
To Reproduce
Create a new project and add browser-extension
vue create my-project
(V3 basic)cd my-project
vue add browser-extension
npm run serve
/dist
folder as an 'unpacked' extension to chromechrome://extensions/
url.Expected behavior There should not be source map errors on default clean install?