Skip to content

Missing require() in next.config.js #78

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ehmicky opened this issue Jan 8, 2021 · 0 comments · Fixed by #99
Closed

Missing require() in next.config.js #78

ehmicky opened this issue Jan 8, 2021 · 0 comments · Fixed by #99
Labels
type: bug code to address defects in shipped code

Comments

@ehmicky
Copy link

ehmicky commented Jan 8, 2021

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug code to address defects in shipped code
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant