Uncaught exception: TypeError: callbacks is not iterable

[JonWallsten]

Describe the bug

I've just upgraded from v4 to v5 and have stumbled upon this error:

[webpack-cli] Uncaught exception: TypeError: callbacks is not iterable 
[webpack-cli] TypeError: callbacks is not iterable 
    at done (C:\Users\me\repo\oas-web\node_modules\webpack\lib\cache\ResolverCachePlugin.js:218:34)
    at C:\Users\me\repo\oas-web\node_modules\webpack\lib\cache\ResolverCachePlugin.js:160:28
    at jobError (C:\Users\me\repo\oas-web\node_modules\webpack\lib\FileSystemInfo.js:1559:5)
    at C:\Users\me\repo\oas-web\node_modules\webpack\lib\FileSystemInfo.js:1795:8
    at C:\Users\me\repo\oas-web\node_modules\webpack\lib\util\AsyncQueue.js:104:29
    at processTicksAndRejections (internal/process/task_queues.js:79:11)

According to the source code it assumes that it can only be and array or undefined even though false is set in the code itself.
It might be a another bug causing the false, but it should be handled, right?

What is the current behavior?

It fails every time I start my DevServer.

To Reproduce

Steps to reproduce the behavior:

We have a pretty complex setup with a monorepo. It's going to be hard to share. But if it's needed to fix the code I guess I can put in the time.

Expected behavior

Build should not fail when I start my DevServer

Please paste the results of webpack-cli info here, and mention other relevant information
System:
OS: Windows 10 10.0.17763
CPU: (12) x64 Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz
Memory: 4.54 GB / 15.81 GB
Binaries:
Node: 12.16.1 - C:\Program Files\nodejs\node.EXE
Yarn: 1.16.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.13.4 - C:\Program Files\nodejs\npm.CMD
Browsers:
Chrome: 86.0.4240.111
Edge: Spartan (44.17763.831.0)
Internet Explorer: 11.0.17763.771

[alexander-akait]

Something wrong with loader, it is not problem with webpack-cli, please provide reproducible test repo

[JonWallsten]

@evilebottnawi : I see, then it's probably something wrong with Angular's tooling I use @ngtools/webpack and I saw some references to an Angular module while debugging. Not sure where to begin though. Care to explain why it's set to false and why false should not be handled by the code? So I can explain in the bug report to Angular? Thanks!

[alexander-akait]

Care to explain why it's set to false and why false should not be handled by the code?

Because false means nothing was found, and other plugins can do additional search

So I can explain in the bug report to Angular?

Yes

If you provide reproducible test repo I can search where it happens

[JonWallsten]

If you provide reproducible test repo I can search where it happens

Sure. Give me a few hours to set it up. Thanks!

[JonWallsten]

@evilebottnawi: I've created a repo now by removing most of our code but leaving the structure. One thing that differ though is that in my repro the web-lib-core library is completely missing __webpack_require__ for some reason. That is not happening in our app right now. So to get to the real problem I need help with understandning why this is happening.
Close this repo:
https://github.com/JonWallsten/monorepo-new/tree/angular%2Bwebpack-upgrade
I sent you an invite since it's private. Create an issue with any questions about installing/running. I'll answer as fast as I can.

[alexander-akait]

Thanks, I will look at this in near future, sorry a lot of issue after webpack@5, we are working on it

[JonWallsten]

Thanks, I will look at this in near future, sorry a lot of issue after webpack@5, we are working on it

No stress! I'm just trying to stay ahead. We don't have to upgrade any time soon.

[alexander-akait]

@JonWallsten How I can reproduce it? I have only warnings and deprecation messages and couple of problems with invalid export, but no problem as you described above

[JonWallsten]

@evilebottnawi I'm unable to reproduce it in the stripped repo. Can only do it in our real repo. Will try do add some more stuff to the repro so we can reproduce it.

[JonWallsten]

@evilebottnawi: I'm having a hard time creating this repro bacause I can't get past the __webpack_require__ is not defined error, and I don't get why it can't. It works in our main repo and it works fine in Webpack 4. Aslo the code looks fine. But I might net get eval completely. Take a look at this:

It passes webpack_require to the function calling eval.
When looking at it with DevTools you can see that it's defined. So why is it missing when calling eval? Isn't that using the current scope?

Here's the scope:

Edit: I got past the error by using inline-source-map instead. Will try to recreate the actual error now.

[alexander-akait]

webpack_require is not defined

Can't help without reproducible test repo

[JonWallsten]

@evilebottnawi: In the branch where it fails result is defined as this:

I have tried to import stuff from Material dialog in the repro-branch to force this, but it never has a result with that file.
I don't have enough knowledge about ResolverCachePlugin to understand what has to happen for a file to end up in this process. Do you mind helping me out, please?

[alexander-akait]

Sorry I can't help, if you provide more stack trace maybe I can, if you create reproducible test repo we will fix it today, we already lost many time...

[alexander-akait]

Do you use boilerplaces? What is versions? Do you try latest version? Which plugin you use, because some of them still have problems with webpack@5