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
This was my own stupidity, but I spent a while debugging why it was failing to even begin the Webpack build and just hanging, before realising I had left a call to the BundleAnalyzerPlugin module in my Webpack production config. Removing/commenting this module fixed the issue. Not sure if it's possible to produce an error/warning for this in the future, but obviously it works locally but then silently fails in the build process.
Thanks again for the module.
The text was updated successfully, but these errors were encountered:
What do you think about the idea to be able to configure a timeout for the webpack task and after the timeout fail the task anyway and give a warning like:
The webpack task couldn't be finished in ${timeout}ms. Maybe the webpack-cli is running in watch mode or using bundle analyzer plugin?
This was my own stupidity, but I spent a while debugging why it was failing to even begin the Webpack build and just hanging, before realising I had left a call to the BundleAnalyzerPlugin module in my Webpack production config. Removing/commenting this module fixed the issue. Not sure if it's possible to produce an error/warning for this in the future, but obviously it works locally but then silently fails in the build process.
Thanks again for the module.
The text was updated successfully, but these errors were encountered: