chore: configure TypeScript project references - #330
Merged
Conversation
This was referenced Sep 10, 2026
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
1 participant
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.
The workspace previously typechecked each package independently and pulled sibling source trees into dependent TSConfig scopes. That blurred project boundaries and forced example tests to reach into the main package through fragile deep relative paths. This PR adds a root solution TSConfig, models package dependencies with project references, narrows every subproject to its own files, and introduces an
@nitro-sqlite/*alias for internal example imports.The core package emits declaration-only reference artifacts into an ignored
.tsbuilddirectory, while the example and vec projects build their declared dependencies during standalone typechecks. The imports added by #320 now use the alias.