-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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 adapter 1.0.0-next.62 build errors with Cannot find module..
#5543
Comments
Is this causing an application failure, or is it just a noisy error message? The dependencies it's failing to resolve are wrapped in a try-catch inside mongoose code, e.g.: let BSON = require('bson');
try {
// Ensure you always wrap an optional require in the try block NODE-3199
BSON = require('bson-ext');
}
catch { } // eslint-disable-line
If you do need those modules, you can simply install them. If you don't, you should be able to safely ignore the message. We should make it look a bit less intimidating though. |
* make resolution failures more appealing - closes #5543 * lint
closed via #5551 on the assumption that the warnings are harmless; please open a new issue if not |
Hi @Rich-Harris , |
Describe the bug
mongoose
, post the version1.0.0-next.60
the build breaks with multiple errors ofCannot find module..
Build log
Workaround
revert to version 1.0.0-next.60
build log
Reproduction
Logs
System Info
Severity
serious, but I can work around it
Additional Information
No response
The text was updated successfully, but these errors were encountered: