fix: fix library export paths #531
Open
+5
−1
Conversation
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
c0state
commented
Jan 7, 2026
| ] | ||
| }, | ||
| "release": { | ||
| "publishDir": "lib", |
Contributor
Author
There was a problem hiding this comment.
The exports above included lib, so this mismatched. Instead, just publish from root, and use the files configuration (see right hand diff) to explicitly define what is included in the published package.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes a packaging issue in v6.0.0-beta.0 where the published package root did not contain the expected ./lib/ tree, causing Node to fail resolving the package via the exports map (MODULE_NOT_FOUND for lib/index.js).
This keeps the package ESM-only.