Repository navigation
fix: tighten TypeScript and package API boundaries - #880
Merged
Merged
Conversation
…undaries fix: tighten TypeScript and package API boundaries
|
@Dev-AdeTutu Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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.
Summary
This PR hardens the SDK's type-safety and package API boundaries across the repository:
@stellar/stellar-sdkto13.3.0in both the development and peer dependency manifests, with the lockfile updated to match.sorokit-core/sharedpackage export with a generated curated public entrypoint instead of exposing the broad internal shared barrel. Internal shared utilities remain available to the implementation but are no longer part of the consumer-facing stability surface.Validation
npm run typechecknpm run buildnpm run validate:exportsCloses #797
Closes #796
Closes #795
Closes #792