This error seems to happen frequently in production.

Looking into individual instances of it, it seems like this happens when the site's next.config.js includes a require() statement towards a dependency that is not installed in package.json, or when there is a typo in the required path.

This is a user error. However, I wanted to report this in case there was a reason why this user error seems to be so frequent. I am wondering whether this is normal for so many sites seem to have invalid next.config.js?