-
Notifications
You must be signed in to change notification settings - Fork 2.4k
feat(manifest): add ./types export with separate type and default entries #27489
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
Conversation
|
Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs). |
|
Can you review this @queengooborg? |
queengooborg
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your PR! This is looking good overall, there's just a couple of things to fix.
The first one is in the below review comment.
The second: may we also update the package.json in the root folder to mirror these changes?
Co-authored-by: Queen Vinyl Da.i'gyu-Kazotetsu <[email protected]>
|
Thanks for your review @queengooborg |
queengooborg
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, looks great! This will be included in today's release!
Summary
This PR adds a new
./typessubpath export to the generated manifest. It separates thetypesand default fields to better support tools and consumers that reference type definitions directly.Test results and supporting details
See Node.js package exports documentation: https://nodejs.org/api/packages.html#exports
Related issues
Fixes failing tests at microsoft/TypeScript-DOM-lib-generator#2104