Open Sebarkar opened 4 years ago
Yes i have the same issue, but its happening from fusioncharts on production mode.
I have the same issues:
I guess that main reason for that is validation checks in library code like process.env.NODE_ENV !== 'production'
.
The process
object during the building stage provides information about the current Node.js process. But in runtime it belongs to browser.
I'm using webpack as a bundler.
Any thoughts?
Just wanted to chime in to say I'm seeing this issue as well. It appears that the entire dev mode version of Vue (version 2.5.17) is included in both the dist/vue-fusioncharts.js
and dist/vue-fusioncharts.min.js
files. Most people will already be importing Vue with their own bundler or via CDN and don't need this other copy showing up.
`import VueFusionCharts from 'vue-fusioncharts'; import FusionCharts from 'fusioncharts'; import Charts from 'fusioncharts/fusioncharts.charts'; import FusionTheme from 'fusioncharts/themes/fusioncharts.theme.fusion';
Vue.use(VueFusionCharts, FusionCharts, Charts, FusionTheme);`
When I commented this code Vue working as expected.