Skip to content

add missing items from user issues #4064

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Oct 14, 2020
Merged

add missing items from user issues #4064

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion src/content/migrate/5.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,6 +105,7 @@ Yarn: `yarn add webpack@next -D`
- When using `[hash]` placeholder in webpack configuration, consider changing it to `[contenthash]`. It is not the same, but proven to be more effective.
- If you are using Yarn's PnP and the `pnp-webpack-plugin`, we have good news: it is supported by default now. You have to remove it from the configuration.
- If you are using `IgnorePlugin` with a regular expression as argument, it takes an `options` object now: `new IgnorePlugin({ resourceRegExp: /regExp/ })`.
- If you are using `node.something: 'empty'` replace it with `resolve.fallback.something: false`.

If you were using WebAssembly via import, you should follow this two step process:

Expand All @@ -114,7 +115,7 @@ If you were using WebAssembly via import, you should follow this two step proces
Reconsider `optimization.splitChunks`:

- It's recommended to use either the defaults or `optimization.splitChunks: { chunks: 'all' }`.
- When using a custom configuration, replace `name` with `idHint`.
- When using a custom configuration, drop `name: false` and replace `name: string | function` with `idHint: string | function`.
- It was possible to turn off the defaults by setting `optimization.splitChunks: { default: false, vendors: false }`. We don't recommend doing this, but if you really want to get the same effect in webpack 5: `optimization.splitChunks: { default: false, defaultVendors: false }`.

Consider removing defaults:
Expand Down