Deprecate baseUrl
compiler option in TypeScript 6.0
#62389
Draft
+1,550
−1,094
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 PR implements deprecation of the
baseUrl
compiler option, which will be removed in TypeScript 7.0. ThebaseUrl
option currently performs two functions that can be confusing to users:paths
Problem
When users configure:
An import like
import * as blah from "blah.js"
might resolve to:./src/app/blah.js
./src/lib/blah.js
./src/blah.js
The last resolution path is usually unintentional and can cause confusion.
Solution
Starting in TypeScript 6.0, using
baseUrl
will show a deprecation warning:Users should migrate to explicit path mappings:
Before:
After:
To preserve baseUrl fallback behavior (optional):
Implementation
src/compiler/program.ts
using existing deprecation infrastructureignoreDeprecations: "6.0"
to silence warnings during transition periodignoreDeprecations
to prevent test breakageFixes #62207.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.