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
Hi r3code team. I am fairly new to VUE and JS in general, and it is very possible that this issue is something that I have done wrong, but it seems to have something to do with having vue-vis-network component and setting the node_env environment variable to production. That being said, when I run my app with node_env set to development, everything seems to work perfectly fine. I would greatly appreciate if someone could give me a hand with this issue.
Also, I am currently using Webpack and vue-cli-service build to minify the app and serve it in production
This is how my app is set up:
//main.js
import { Network } from 'vue-vis-network';
import App from '@/App.vue';
import router from '@/router';
import store from '@/store';
Vue.component('network', Network);
new Vue({
router,
store,
render: (h) => h(App),
}).$mount('#app');
I am experiencing very similar issue. Although I'm not using vue-vis-network. Suggesting this might have something to do with vue and vue's build tooling.
Same problem here. Interesting, but if I clear :options for vis-network and use just empty object - all worked fine in dev and prod mode. But if I set hierarchical layout in options, then page freeze in prod mode. May be this help.
Hi r3code team. I am fairly new to
VUE
andJS
in general, and it is very possible that this issue is something that I have done wrong, but it seems to have something to do with havingvue-vis-network
component and setting thenode_env
environment variable toproduction
. That being said, when I run my app withnode_env
set todevelopment
, everything seems to work perfectly fine. I would greatly appreciate if someone could give me a hand with this issue.Also, I am currently using
Webpack
andvue-cli-service
build to minify the app and serve it in productionThis is how my app is set up:
The text was updated successfully, but these errors were encountered: