You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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 arequire()
statement towards a dependency that is not installed inpackage.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
?The text was updated successfully, but these errors were encountered: