You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/migrate/5.mdx
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,7 @@ contributors:
13
13
- getsnoopy
14
14
- yevhen-logosha
15
15
- akash-kumar-dev
16
+
- EvanSanderson
16
17
---
17
18
18
19
This guide aims to help you migrating to webpack 5 when using webpack directly. If you are using a higher level tool to run webpack, please refer to the tool for migration instructions.
@@ -292,6 +293,10 @@ Repeat the following steps until you solved at least level 3 or 4:
292
293
- 404 errors pointing to URLs containing `auto`
293
294
- Not all ecosystem tooling is ready for the new default automatic `publicPath` via `output.publicPath: "auto"`
294
295
- Use a static `output.publicPath: ""` instead.
296
+
- Cannot read properties of undefined (reading 'call')
297
+
- If you see this error during runtime, it may be related to the [ModuleConcatenationPlugin](https://webpack.js.org/plugins/module-concatenation-plugin/). Check if you are using the plugin, and if you've included it in the `plugins` sections of a config, and that config is also set to `production` mode, remove the plugin (ie `new webpack.optimize.ModuleConcatenationPlugin()`) from your plugins list. In webpack 5, the plugin is enabled by default in production mode, and it may get included twice.
298
+
- In general, disabling each plugin and testing the build is a good way to triage where the issue might be coming from.
299
+
- See: [this issue](https://github.com/webpack/webpack/discussions/15369#discussioncomment-13420496) for more details.
0 commit comments