Firefox Extension Not Working Anymore #1023
-
|
I am having issues with the Firefox extension that used to work just fine with our Laravel/Vue3 project. I would like some help troubleshooting as I don't want to switch to Chrome, where it works for me. Symptoms
Attempted Fixes
I looked at the only item on the "troubleshooting" page and I'm not seeing the config file referenced nor any of the code in my codebase. I don't think we set up the vite plugin, the extension just worked from when I started using it several years ago and has not been working since I recently came back to the Laravel/Vue3 project we are working on. I also noticed that the Firefox extension is not listed on the "installation" page, but the last update according to Firefox was December 3, 2025. I can't imagine the extension is no longer supported? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
this is a known issue with firefox and vue devtools. happens because of how firefox handles extension permissions and content scripts. try these fixes:
// vite.config.js
export default {
define: {
__VUE_PROD_DEVTOOLS__: true // force enable in prod
}
}
// webpack.mix.js
mix.webpackConfig({
resolve: {
alias: {
vue$: "vue/dist/vue.esm-bundler.js"
}
}
});
const app = createApp(App);
app.config.devtools = true; // explicitly enable
the extension is still supported for firefox, just has some compatibility issues with newer firefox versions. chrome version is more stable if you need it working urgently. |
Beta Was this translation helpful? Give feedback.
-
|
We decided to replace mix with vite because mix is no longer being actively maintained and it wasn't too hard to throw into the queue. As a result, the extension works fine now. I really appreciate your help @ismaildasci but it seems we solved our own problem unintentionally! |
Beta Was this translation helpful? Give feedback.
We decided to replace mix with vite because mix is no longer being actively maintained and it wasn't too hard to throw into the queue. As a result, the extension works fine now. I really appreciate your help @ismaildasci but it seems we solved our own problem unintentionally!