Breaking webpack production builds
See original GitHub issueUglify does not support let
statements. Due to the recent release many webpack production builds are failing because of this.
Issue Analytics
- State:
- Created 6 years ago
- Comments:16 (4 by maintainers)
Top Results From Across the Web
Production | webpack
In this guide, we'll dive into some of the best practices and utilities for building a production site or application.
Read more >production build breaks with optimization, if webpack plugin ...
The error occurs, while using a webpack plugin that creates a less file inside the production build. If optimization is false, it works....
Read more >Webpack 5 production mode result in a broken app
I had a similar issue, broken production build with no errors, but the code did not enter the main entry-point. Stumped for hours....
Read more >Managing Dev and Production Builds with Webpack
Managing Dev and Production Builds with Webpack. January 31, 2018 ... This of course will break if there is no drupalSettings object.
Read more >How to boost the speed of your webpack build?
Use Speed Measure Plugin to debug webpack build time · Track your build time evolution to detect big evolution before merge · Follow...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I released
v1.0.1
withvar
switched out in favour oflet
andconst
.Hopefully this shouldn’t break webpack builds.
I just published 1.1.2 of react-side-effect rolling back the shallowequal dependency to resolve the broken builds.
No good deed goes unpunished, right? 😅 Thanks for prompt reply @dashed