-
Notifications
You must be signed in to change notification settings - Fork 54
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
Plugin is not working with new new web dev server #73
Comments
@gajus do you know how to fix the plugin if futureEmitAssets is true ? |
I do not. PR is welcome. |
I've notice that they have the same problem. |
Any updates on this? It seems like anything that reads the asset after it's been emitted will throw based on this: webpack/webpack#8642 It seems like |
Anyone is welcome to contribute a solution. |
@gajus At now there is a workaround. I have posted it in first post: |
Hello, after upgrading from
I've added to my development configuration the mentioned option and it works as expected : module.exports = {
// your other options
optimization: {
// Your optimization options
},
plugins: [
// your plugins
],
devServer: {
devMiddleware: {
writeToDisk: true, // <= what you need to add
},
},
}; Hope this helps. |
Due to this commit add output.futureEmitAssets your plugin is not working anymore on new web dev server.
Do you have a workaround?
Edit:
I found the work around:
The text was updated successfully, but these errors were encountered: