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
I been using previous versions to this update and switching to production has no problem. However, with the latest build I had last night, I ran into issues where I can't switch to production no matter what I do. It runs all the prod scripts, hides modules, etc. But when I run it, it says:
vue.js:9057 You are running Vue in development mode.
Make sure to turn on production mode when deploying for production.
See more tips at https://vuejs.org/guide/deployment.html
client.js:92 [HMR] connected
In the google console.
And when I deploy to IIS, it gives me a server side error:
One or more errors occurred. (Webpack dev middleware failed because of an error while loading 'aspnet-webpack'. Error was: Error: Cannot find module 'aspnet-webpack'
I'm not sure why it still thinks I'm on dev no matter what I do.
And it ran well. All the scripts executed successfully, but I still get the same errors. If I run other projects that I had based on this repo, I didn't run into these issues.
The text was updated successfully, but these errors were encountered:
I been using previous versions to this update and switching to production has no problem. However, with the latest build I had last night, I ran into issues where I can't switch to production no matter what I do. It runs all the prod scripts, hides modules, etc. But when I run it, it says:
In the google console.
And when I deploy to IIS, it gives me a server side error:
One or more errors occurred. (Webpack dev middleware failed because of an error while loading 'aspnet-webpack'. Error was: Error: Cannot find module 'aspnet-webpack'
I'm not sure why it still thinks I'm on dev no matter what I do.
I even created this bat file:
And it ran well. All the scripts executed successfully, but I still get the same errors. If I run other projects that I had based on this repo, I didn't run into these issues.
The text was updated successfully, but these errors were encountered: