fix: reorder exports to place types first#1261
Merged
Merged
Conversation
|
|
Garbee
approved these changes
Jan 6, 2026
Member
Garbee
left a comment
Garbee
left a comment
There was a problem hiding this comment.
The ordering is correct per Node docs.
Thank you for putting the time into this.
Contributor
|
Approved for security. |
Merged
straker
added a commit
that referenced
this pull request
Jan 12, 2026
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Move the "types" condition to the first position in package.json
exports field to align with Node.js conditional exports standards.
This ensures TypeScript properly resolves type definitions.
Closes: #1243