Cannot read properties of undefined (reading 'call') #15369
Replies: 3 comments 5 replies
-
Please create reproducible test repo |
Beta Was this translation helpful? Give feedback.
-
Not possible because it's a client's project and I know for a fact issue is related to this specific project because for another project I am running the latest webpack without issues. @alexander-akait I need to know way to debug it. the error it gives is not clear. Is there anyway I can get a proper error which I can understand and fix? |
Beta Was this translation helpful? Give feedback.
-
@Musadiqkhan-nullbrainer we had this same exact issue (not just the error, but also downgrading to 5.24.0 versus 5.24.1 would fix things). in our case we had the you may have some plugin causing an issue in your production config, try disabling them one by one and see if the error persists. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Bug report
What is the current behavior?
Upgraded to latest webpack version from webpack 5.23.0 and encountered a runtime error
Cannot read properties of undefined (reading 'call') at __webpack_require__ (app.8dfc72f16583797bed7d.js:2:1594857)
. Downgraded to find out the issue starts showing up from webpack 5.24.1This is most probably due to improve performance of finding modules to concatenate. If I set optimization.concatenateModules to false then everything works fine.
I have found out list of outdated packages using
npm outdated
. Updated them to wanted version and still facing the issue.How can I find the real cause?
Other relevant information:
webpack version: 5.68.0
Node.js version:
Operating System: Windows
Additional tools:
Beta Was this translation helpful? Give feedback.
All reactions