-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Webpack 4 migration? #292
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I'm currently working on a Pull Request at the moment. All is functioning in development mode, but still working on a patch for the "extract-text-webpack-plugin" which is causing an error in production mode. Webpack 4.0 is still quite buggy, as many plugins aren't updated as of yet. |
@larkin-nz I realised it as well some warnings with extract-text-webpack-plugin. Existing webpack 4 upgrade pull request works with similar warnings but it produces the bundle correctly and works for me. What error do you receive? |
The issues that I'm having occurring in production mode are causing Webpack not to serve the CSS files to the browser. |
This sounds slightly similar issue I was having when I upgraded webpack-dev-middleware to 3.x but had to revert back to 2.x. The issue I was having was on Windows OS and it was for all static files not being served because of some path malformed. But yours might be a different issue. |
Interesting, I'm running a Unix-like architecture and it seems to run fine in development mode. I'll do some debugging tomorrow and have a look at that. |
I'm also looking forward to this working with Vue 4.x |
Any updates on this ? Looking forward to it. |
Any plans of migrations to webpack 4?
The text was updated successfully, but these errors were encountered: