Please sign in to comment.
The principal motivation for that is to apply a minification to a production bundle which is available via webpack > 4 version It is also a good practice to have close to latest dependencies which have been fixed in order to ensure a maximal reproducibility of a build. Also: - add/fix scripts for running webpack and webpack-dev-server - fix some incompatibility issues with d3.js - webpack demands now an environment to be set which is done by setting NODE_ENV - regenerated whole yarn.lock
- Loading branch information...
Showing with 4,344 additions and 2,739 deletions.
- +35 −32 package.json
- +11 −3 webpack.config.js
- +4,285 −2,698 yarn.lock
Oops, something went wrong.