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
Currently, the package parser includes support for non-exports entrypoints:
exports
main
module
jsnext:main
types
However, as both npm and Node 16+ supports exports which provides nicer syntax for e.g. multiple entries, let's remove support for legacy fields.
The text was updated successfully, but these errors were encountered:
Merge pull request #246 from Comandeer/t/228
ff7e09a
Closes #228
Comandeer
Successfully merging a pull request may close this issue.
Currently, the package parser includes support for non-
exports
entrypoints:main
,module
/jsnext:main
types
.However, as both npm and Node 16+ supports
exports
which provides nicer syntax for e.g. multiple entries, let's remove support for legacy fields.The text was updated successfully, but these errors were encountered: