feat: respect the references in tsconfig files - #121
Merged
Conversation
|
I have the same issue - thanks for sharing the solution. 🌟 |
0xcadams
self-requested a review
June 27, 2025 21:40
Member
|
Wow, this is excellent. Thanks for opening a PR! I will get a release out today. |
0xcadams
approved these changes
Jun 27, 2025
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
3 participants
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.
It seems that
ts-morphdoes not resolve the references in tsconfig files.Rather than waiting for dsherret/ts-morph#876 to be fixed (it was opened in 2020), I'm pushing this workaround directly here instead.
This will allow drizzle-zero to work in a monorepo context where the drizzle schema is defined in a different package from the apps that use zero.