break: require TypeScript >= 6.0#11915
Merged
Merged
Conversation
slorber
added
the
pr: breaking change
✅ [V2]
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Size Change: 0 B Total Size: 12 MB ℹ️ View Unchanged
|
⚡️ Lighthouse report for the deploy preview of this PR
|
|
Size Change: 0 B Total Size: 12.4 MB ℹ️ View Unchanged
|
nmschulte
added a commit
to nmschulte/fome-wiki
that referenced
this pull request
Apr 22, 2026
nmschulte
added a commit
to FOME-Tech/wiki
that referenced
this pull request
Apr 22, 2026
* tsc: ignore v6 deprecations facebook/docusaurus#11893 facebook/docusaurus#11915 * try fix DbcViewer typescript
3 tasks
Zodiarche
added a commit
to PokemonWorkshop/PokemonWorkshopDocs
that referenced
this pull request
May 14, 2026
TypeScript 6.0 deprecates the 'baseUrl' compiler option (TS5101). The 'baseUrl' is set in @docusaurus/tsconfig itself, so it must stay for the '@site/*' path mapping to keep resolving — we cannot drop it from our project's tsconfig. Add 'ignoreDeprecations': '6.0' to tsconfig.json to silence the deprecation warning. This is the official workaround recommended by the Docusaurus team in facebook/docusaurus#11893 and by TypeScript itself in the error message. The proper fix (removing 'baseUrl' from the shared @docusaurus/tsconfig) is planned for Docusaurus 4.0 via PR facebook/docusaurus#11915; we can drop 'ignoreDeprecations' then. Bundles the TypeScript bump in the same commit because TS 5.6 rejects 'ignoreDeprecations: 6.0' as an invalid value, so splitting the change would break typecheck temporarily. Closes #9
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.
Motivation
Follow up on #11843
Fix #11893
Scheduled for Docusaurus v4 (breaking change), see #11719
We want to require TypeScript v6.0+, which helps simplify our base TS config + the local site config + our complex CI setup.
Since v7 is a Go rewrite that is supposed to be compatible with v6.0, Docusaurus v4 should also be ready for TypeScript 7.0.
TypeScript v6.0 release notes: https://devblogs.microsoft.com/typescript/announcing-typescript-6-0/
A site TS config could now be as simple as this:
{ "extends": "@docusaurus/tsconfig", }@sitealias and excludes are now fully encapsulated iunto the base config, thanks to TS 5.5+{configDir}placeholder (ref)Technically, it should remain possible to keep using TS < 6.0 with Docusaurus v4. However, you won't be able to use our base config: you'd need to copy its content
Test Plan
CI
Test links
https://deploy-preview-11915--docusaurus-2.netlify.app/