Thanks for the quick response!
Just to add - downgrading from webpack@5.101.0 to 5.100.2 resolved the issue for me. This suggests that something introduced in 5.101.0, possibly an internal utility or updated dependency, may be triggering the require('node:url') call - even if not directly inside the webpack core code.

Sorry we can't fix something somewhere, please create reproducible test repo

Thanks for the response. Unfortunately, I'm unable to create a reproducible repository right now due to limited time. Just wanted to flag this in case others encounter the same issue after updating to webpack@5.101.0. Downgrading to 5.100.2 consistently resolves it for me.

Please stop repeat Downgrading to 5.100.2 consistently resolves it for me. it doesn't help to solve your problem, we don't use node: inside webpack, just look at our code, your project can have a lot of other deps where it can happen, also v20.19.4 NodeJS supports node: protocol, so I can't help your here without additional information