Skip to content

FRONTIER-4800: widen TypeScript peer range to allow TypeScript 6 #432

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
joeycozza merged 2 commits into from
Sep 9, 2026
Merged

FRONTIER-4800: widen TypeScript peer range to allow TypeScript 6 #432

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0f76788
FRONTIER-4800: widen typescript peer range to allow TypeScript 6
dvjensen17 Sep 3, 2026
574de9b
FRONTIER-4800: bump @fs/react-scripts to 8.16.4 and add changelog entry
joeycozza Sep 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions CHANGELOG-FRONTIER.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,11 @@
## 8.16.4

- Widen the `typescript` peer range from `^3.2.1 || ^4 || ^5` to `^3.2.1 || ^4 || ^5 || ^6` so consuming apps can take `typescript@6`
- npm 7+ enforces peer ranges for optional peers that are actually present in the tree, so any repo upgrading to `typescript@^6` hit an `ERESOLVE` conflict on `npm install` — including plain-JavaScript repos that only pull TypeScript in for lint and type-check tooling. Teams were closing or excluding their Renovate TypeScript 6 PRs to work around it, which also silences future 6.x notifications
- react-scripts touches TypeScript in three places — `verifyTypeScriptSetup.js`, `ForkTsCheckerWebpackPlugin` (via react-dev-utils), and `@babel/preset-typescript` for transpilation. TypeScript 6.x is the bridge release line that keeps the JavaScript-based compiler and its in-process compiler API, so all three behave as they do under 5.x
- `^7` is deliberately excluded: TS 7 is the native (Go) compiler and does not expose the in-process JS compiler API that fork-ts-checker and `verifyTypeScriptSetup` depend on, so declaring it would trade today's up-front `ERESOLVE` for a runtime build failure. `^3.2.1 || ^4` is deliberately kept — narrowing a peer range is breaking for consumers still on older TS
- Purely additive for existing consumers on TS 3/4/5. Note that this repo's own CI still runs `typescript: ^4.4.4`, so TS 6 is not exercised here; verified by smoke test in `fs-eng/data-dmconsole` at `typescript@6.0.3` (clean `npm install`, passing production build, passing tests)

## 8.16.3

- Migrate CI from Travis to GitHub Actions (`.github/workflows/ci.yml`); delete `.travis.yml`
Expand Down
4 changes: 2 additions & 2 deletions packages/react-scripts/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@fs/react-scripts",
"version": "8.16.3",
"version": "8.16.4",
"upstreamVersion": "5.0.1",
"description": "Configuration and scripts for Create React App.",
"repository": {
Expand Down Expand Up @@ -145,7 +145,7 @@
"peerDependencies": {
"@fs/eslint-config-frontier-react": ">=10.0.0",
"react": ">= 16",
"typescript": "^3.2.1 || ^4 || ^5"
"typescript": "^3.2.1 || ^4 || ^5 || ^6"
},
"peerDependenciesMeta": {
"typescript": {
Expand Down
Loading