Prepare Commonlib 0.1.13 - #113
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.
This release preparation updates Commonlib to 0.1.13 so TypeScript's Node10 module resolution can resolve declarations for the package root and every supported subpath.
Changes
package.jsonandpackage-lock.jsonfrom 0.1.12 to 0.1.13.typesentry and generatedtypesVersionsmappings introduced in PR Generate TypeScript declaration mappings for public entries #111. Both are derived from the existing public export inventory, so theexportsmap remains authoritative.octagonal-wheels0.1.53, whose generated package provides the corresponding root and subpath declaration mappings.Impact
TypeScript's
Node10module resolution does not use declaration conditions from a package'sexportsmap. The generated manifest now mirrors that map through a top-leveltypesentry andtypesVersions, preventing supported Commonlib imports from degrading to unresolvederrortypes in downstream analysis.This release does not introduce a public entry or change synchronisation, storage, or protocol behaviour.
Verification
npm ciwith npm 11.18.0 succeeded.NODE_OPTIONS=--max-old-space-size=3072 npm run verify:packagesucceeded: 71 test files and 1,283 tests passed, together with seven boundary tests, 20 release-selection tests, type checks, package-boundary checks, 109 generated compatibility exports, and clean-consumer checks.Node10module resolution.npm publish --dry-run .package --tag next --access publicsucceeded: 500 files, 405,588 bytes packed, and 1,751,037 bytes unpacked.sha512-uqFiccRbTQTY8M7RzI68SMjfms65w0MsgrqIKwoTLJkrqnXPdxoJHR4eV6Q4vq7OLWvBMjQOeGy+3mLXfXSrFA==.39732904858ed1889a5a8bde6a6c6f27b2fdcb02. The official Obsidian Community ESLint configuration no longer reported the targetederror-typed union or intersection findings.31712668655repeated package verification and managed integration against release head1ae3855cbd99a882470ed6cf50c11e72bbeb1087; Package verification, Integration tests, and Complete package gate all succeeded.31713088266packed that exact release head, installed@vrtmrz/livesync-commonlib@0.1.13into Self-hosted LiveSync commit39732904858ed1889a5a8bde6a6c6f27b2fdcb02, and passed the downstream type and unit checks, plug-in, CLI, WebApp, and WebPeer builds, and CLI end-to-end test.