We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Now the rgbpp-sdk only exports CommonJS package, and it will cause a Named Exports issue when developers use ESM to import rgbpp-sdk like this:
rgbpp-sdk
"Named export 'Types' not found. The requested module 'mongoose' is a CommonJS module, which may not support all module.exports as named exports"
reference: https://stackoverflow.com/questions/70605320/named-export-types-not-found-the-requested-module-mongoose-is-a-commonjs-mo
To avoid potential issues, it is recommended to export an ESM package for rgbpp-sdk.
The text was updated successfully, but these errors were encountered:
duanyytop
ShookLyngs
Successfully merging a pull request may close this issue.
Now the
rgbpp-sdk
only exports CommonJS package, and it will cause a Named Exports issue when developers use ESM to importrgbpp-sdk
like this:"Named export 'Types' not found. The requested module 'mongoose' is a CommonJS module, which may not support all module.exports as named exports"
To avoid potential issues, it is recommended to export an ESM package for
rgbpp-sdk
.The text was updated successfully, but these errors were encountered: