add missing items from user issues (#4064)

Author: sokra

src/content/migrate/5.md

@@ -106,6 +106,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:
 
@@ -115,7 +116,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: