-
Notifications
You must be signed in to change notification settings - Fork 63
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
Vercel build error "Error [ERR_REQUIRE_ESM]: require() of ES Module /path/to/node-fetch not supported." #1290
Comments
Hey @wscourge, thanks for reporting this! I just tried with a minimal example app and I'm also getting an error (though different from what you reported). I will take a deeper look and write here when I have updates. |
OK sure thanks for getting back to me @subzero10. I can give you access to a fork of the private repo that fails so you can clone it and reproduce my exact error, if it helps. Let me know. |
Hey @wscourge, that'd be great. Can you please do that? |
OK I'm doing it, gimme 10min |
I sent you an invite. Please do the following:
LMK if I can help you any further, cheers |
Hey @wscourge, I couldn't fork the repository (forking is disabled), but here's what I did:
I didn't change anything other than the config that points to the new vercel domain. I also added a button to report to Honeybadger (it reports to my HB project). |
Hey @wscourge, Any updates on this? I'd love to help out but I will need a reproducible example. |
What are the steps to reproduce this issue?
What happens?
What were you expecting to happen?
Build passes
Any logs, error output, etc?
full backtrace
Any other comments?
full package.json
What versions are you using?
Operating System: whatever's on vercel
Package Name: next
Package Version:
Browser Version: n/a
The text was updated successfully, but these errors were encountered: