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
When using vuex in Vue application, @vue/devtools-api will always be part of final bundle.
If we take a look at vuex.cjs.js
var vue = require('vue');
var devtoolsApi = require('@vue/devtools-api');
we can conclude that @vue/devtools-api code will be part of final bundle. Tree shaking doesn't work here because adding devtools happing in runtime, during install function execution.
Is there way to exclude @vue/devtools-api code?
Steps to reproduce:
Run vite build
I am using Vuex: "4.1.0"
What is expected?
There is no @vue/devtools-api code in final bundle if dev tools is disabled through bundler tool.
What is actually happening?
There is @vue/devtools-api code in final bundle.
I am using Vuex: "4.1.0"
The text was updated successfully, but these errors were encountered:
Version
4.1.0
Reproduction link
github.com
Steps to reproduce
When using vuex in Vue application, @vue/devtools-api will always be part of final bundle.
If we take a look at
vuex.cjs.js
we can conclude that @vue/devtools-api code will be part of final bundle. Tree shaking doesn't work here because adding devtools happing in runtime, during
install
function execution.Is there way to exclude @vue/devtools-api code?
Steps to reproduce:
vite build
I am using Vuex: "4.1.0"
What is expected?
There is no @vue/devtools-api code in final bundle if dev tools is disabled through bundler tool.
What is actually happening?
There is @vue/devtools-api code in final bundle.
I am using Vuex: "4.1.0"
The text was updated successfully, but these errors were encountered: