Release v0.5.0 - #75
Merged
Merged
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
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.
Changes
Fixed
0.4.0. Every subpath'simport.defaultpointed at a.mjsfile the tsup build never produced —publintconfirmed all 8 missing against the published tarball. The tsdown migration below is what actually builds the files theexportsmap has declared since0.4.0.node10module resolution failed for every subpath. AddedtypesVersionsmapping each to its.d.ts.repository.urlnow a fullgit+https://URL.Changed
Verification
Clean-room (
rm -rf node_modules dist && npm ci):check✅,build✅,publint→ All good!,attw→ all 8 entry points 🟢 across node10, node16 (CJS+ESM), bundler.After merge
publish.ymltriggers onrelease: [created]— a bare tag will not fire it.