Commit 967d02d

authored

Update 5.mdx

Add section in troubleshooting tips on Cannot read properties of undefined (reading 'call') error

1 parent cc4785f commit 967d02dCopy full SHA for 967d02d

File tree

-0

lines changed

-0

lines changed

Lines changed: 4 additions & 0 deletions

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

Comments

(0)