Skip to content

Update 5.mdx #7635

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 2 commits into from
Jun 12, 2025
Merged

Update 5.mdx #7635

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
967d02d
Update 5.mdx
EvanSanderson Jun 10, 2025
ad684e3
Update 5.mdx
EvanSanderson Jun 10, 2025
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
5 changes: 5 additions & 0 deletions src/content/migrate/5.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@ contributors:
- getsnoopy
- yevhen-logosha
- akash-kumar-dev
- EvanSanderson
---

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.
Expand Down Expand Up @@ -292,6 +293,10 @@ Repeat the following steps until you solved at least level 3 or 4:
- 404 errors pointing to URLs containing `auto`
- Not all ecosystem tooling is ready for the new default automatic `publicPath` via `output.publicPath: "auto"`
- Use a static `output.publicPath: ""` instead.
- Cannot read properties of undefined (reading 'call')
- 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.
- In general, disabling each plugin and testing the build is a good way to triage where the issue might be coming from.
- See: [this issue](https://github.com/webpack/webpack/discussions/15369#discussioncomment-13420496) for more details.

- Level 6: **Deprecation Warnings**.

Expand Down
Loading