Upgrade Webpack to 3.*
See original GitHub issueThe title is explicit ; we should upgrade Webpack from 1.*
to 3.*
.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
To v4 from v3 - webpack
The installation guide can be found here. Update plugins. Many 3rd party plugins need to be updated to the latest versions to be...
Read more >Webpack upgrade from 3 to 4 - Medium
Before starting with an upgrade to v4, let's discuss the high-level definition of webpack. I promise this won't take much time.
Read more >Migrating from Webpack 3 to 4 - AppOptics Blog
Upgrade node to 8.9.4 · Upgrade webpack · Use a mode · Change CommonsChunkPlugin to splitChunks · Get rid of ModuleConcatenationPlugin · Change ......
Read more >Guides - Migrating from v2 to v3 #1569 - GitHub
zzzgit commented on Sep 3, 2017. i want to update webpack in my project from 2 to 3,but i can not do this...
Read more >Step by Step Migration - Webpack 3 to Webpack 4 - CodeProject
Update the npm version. It should be greater than 8.9.0 . Run command npm -v to check the current version and to upgrade...
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
This issue is somewhat explained in https://github.com/webpack/webpack/issues/4039. Specifically this comment from webpack’s author https://github.com/webpack/webpack/issues/4039#issuecomment-273804003 states that ES6’s
import
statements and CommonJS’smodule.exports
assignments cannot be mixed. After some recent changes,module.exports
has valueundefined
and is read-only when it comes to webpack.A quick and dirty workaround is to remove
modules: false
option from the babel presets in the dependent project’s config. BUT this change disables the tree-shaking offered by webpack 2, so not a great solution.Will try to make a pull request with the migration to webpack 2, but no promises. 😉
This is great, thank you for those precious info!
By the way,
v4
is being delayed for the time being (vacations + working on complex rewrites will not help speed things up 😉), so you have some time to try to create a PR if you want 😃Thanks again!