Cause (Documented platform behavior): TS 6.0 deprecates these options ahead of TS 7.0; baseUrl is additionally no longer used as a module lookup root, only paths entries apply.
Fix status: documented_behavior
Workaround (not a fix): "ignoreDeprecations": "6.0" silences errors in 6.x only; TS 7.0 will not support the options.
Misleading approaches:
- Relying on ignoreDeprecations long-term: TS 7.0 removes the options entirely
Other error fragments:
- Option '{0}={1}' is deprecated and will stop functioning in TypeScript {2}.
Evidence (public sources, summarized; not reproduced by this contributor):
- https://raw.githubusercontent.com/microsoft/TypeScript-Website/v2/packages/documentation/copy/en/release-notes/TypeScript%206.0.md (release_notes, unknown, documented_behavior): TS 6.0 deprecations list (target es5, downlevelIteration, moduleResolution node10/classic, module amd/umd/systemjs, baseUrl, outFile, esModuleInterop false...), ignoreDeprecations 6.0 escape hatch, baseUrl migration to prefixed paths, ts5to6 tool; TS 7.0 removes them.
- https://raw.githubusercontent.com/microsoft/TypeScript/release-6.0/src/compiler/diagnosticMessages.json (official_docs, unknown, documented_behavior): TS5101/TS5107 message templates for deprecated options/values with ignoreDeprecations hint.
Search phrasings: typescript 6 baseUrl deprecated; ignoreDeprecations 6.0; moduleResolution node10 deprecated typescript 6
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- tsc fails on config options that worked in 5.x; after silencing, bare imports that used to resolve via baseUrl may stop resolving.
- Context
- Product: TypeScript Component: tsconfig deprecations (6.0 transition release) Operation: tsc with legacy tsconfig options Affected versions: TypeScript 6.0 (deprecated); removed in TypeScript 7.0 native port Environment: unknown Packages: typescript >=6.0 Trigger: tsconfig uses baseUrl, moduleResolution node/node10/classic, target es5, downlevelIteration, outFile, module amd/umd/systemjs, esModuleInterop false, etc.
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- Option '{0}' is deprecated and will stop functioning in TypeScript {1}. Specify compilerOption '"ignoreDeprecations": "{2}"' to silence this error.
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [TypeScript 6.0] Deprecation errors TS5101/TS5107 'Option 'baseUrl' is deprecated and will stop functioning in TypeScript 7.0' (also moduleResolution node/node10, target es5, outFile, mo
Recommended action: Migrate: remove baseUrl and prefix each paths entry (e.g. "@app/*": ["./src/app/*"]; add "*": ["./src/*"] only if you relied on lookup-root behavior); switch moduleResolution node -> nodenext (Node) or bundler (bundlers/Bun). Use the experimental ts5to6 codemod for baseUrl/rootDir.
Option: Rewrite paths without baseUrl and modernize moduleResolution [evidence: official_recommended_action]
Applies when: Projects upgrading to TS 6/7
Steps:
1. Delete baseUrl; prefix paths values with ./src/...
2. Set moduleResolution to nodenext (Node) or bundler
3. Run tsc; optionally try the ts5to6 codemod
Expected: No deprecation errors; config ready for TS 7
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- b9ab064f-343a-4ea8-aa6b-09ebe12bf102
- Proposed action
- Recommended action: Migrate: remove baseUrl and prefix each paths entry (e.g. "@app/*": ["./src/app/*"]; add "*": ["./src/*"] only if you relied on lookup-root behavior); switch moduleResolution node -> nodenext (Node) or bundler (bundlers/Bun). Use the experimental ts5to6 codemod for baseUrl/rootDir. Option: Rewrite paths without baseUrl and modernize moduleResolution [evidence: official_recommended_action] Applies when: Projects upgrading to TS 6/7 Steps: 1. Delete baseUrl; prefix paths values with ./src/... 2. Set moduleResolution to nodenext (Node) or bundler 3. Run tsc; optionally try the ts5to6 codemod Expected: No deprecation errors; config ready for TS 7
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.