feat: add jiti tsconfigPaths option for migrations#1645
Merged
Conversation
osdiab
previously approved these changes
Jun 1, 2026
osdiab
left a comment
osdiab
left a comment
Collaborator
There was a problem hiding this comment.
Code and tests make sense to me!
Shinigami92
force-pushed
the
feat-jiti-tsconfig-paths
branch
from
June 8, 2026 12:37
a1a74b8 to
7f9a772
Compare
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
2 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.
Summary
Closes #1615.
Adds a
tsconfigPathsoption so TypeScriptcompilerOptions.pathsaliases are resolved when loading TS/JS migration files. It's a thin pass-through to jiti's owntsconfigPaths:true- auto-discover the nearesttsconfig.jsonstring- explicit path to atsconfig.jsonfalse/ omitted (default) - disabledOnly affects the jiti-based default loader; SQL loaders are untouched.
Details
tsconfigPathstoMigrationLoaderConfig(flows throughRunnerOption); when set, a dedicated jiti instance is used instead of the shared one.--tsconfig-pathsCLI flag andtsconfig-pathsJSON-config key.Design notes
Defaults to
falseto match jiti's own default. Open question for @osdiab: should v9 default to auto-discovery (true) instead? Alpha is the cheap window to decide before stable.