(react-scripts) Support for TypeScript 5.x #13080

Torniojaws · 2023-03-22T07:53:20Z

Describe the bug

After npx create-react-app frontend --template typescript, when you update package.json to use "typescript": "^5.0.2",, npm install <any package> fails with this error:

$ npm i react-router-dom
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: react-scripts@5.0.1
npm ERR! Found: typescript@5.0.2
npm ERR! node_modules/typescript
npm ERR!   peer typescript@">= 2.7" from fork-ts-checker-webpack-plugin@6.5.3
npm ERR!   node_modules/fork-ts-checker-webpack-plugin
npm ERR!     fork-ts-checker-webpack-plugin@"^6.5.0" from react-dev-utils@12.0.1
npm ERR!     node_modules/react-dev-utils
npm ERR!       react-dev-utils@"^12.0.1" from react-scripts@5.0.1
npm ERR!       node_modules/react-scripts
npm ERR!         react-scripts@"5.0.1" from the root project
npm ERR!   peer typescript@">=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta" from tsutils@3.21.0
npm ERR!   node_modules/tsutils
npm ERR!     tsutils@"^3.21.0" from @typescript-eslint/eslint-plugin@5.55.0
npm ERR!     node_modules/@typescript-eslint/eslint-plugin
npm ERR!       @typescript-eslint/eslint-plugin@"^5.5.0" from eslint-config-react-app@7.0.1
npm ERR!       node_modules/eslint-config-react-app
npm ERR!         eslint-config-react-app@"^7.0.1" from react-scripts@5.0.1
npm ERR!         node_modules/react-scripts
npm ERR!       3 more (eslint-config-react-typescript, eslint-plugin-jest, the root project)
npm ERR!     tsutils@"^3.21.0" from @typescript-eslint/type-utils@5.55.0
npm ERR!     node_modules/@typescript-eslint/type-utils
npm ERR!       @typescript-eslint/type-utils@"5.55.0" from @typescript-eslint/eslint-plugin@5.55.0
npm ERR!       node_modules/@typescript-eslint/eslint-plugin
npm ERR!         @typescript-eslint/eslint-plugin@"^5.5.0" from eslint-config-react-app@7.0.1
npm ERR!         node_modules/eslint-config-react-app
npm ERR!         3 more (eslint-config-react-typescript, eslint-plugin-jest, the root project)
npm ERR!     1 more (@typescript-eslint/typescript-estree)
npm ERR!   1 more (the root project)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional typescript@"^3.2.1 || ^4" from react-scripts@5.0.1
npm ERR! node_modules/react-scripts
npm ERR!   react-scripts@"5.0.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: typescript@4.9.5
npm ERR! node_modules/typescript
npm ERR!   peerOptional typescript@"^3.2.1 || ^4" from react-scripts@5.0.1
npm ERR!   node_modules/react-scripts
npm ERR!     react-scripts@"5.0.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /home/juha/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/juha/.npm/_logs/2023-03-19T13_21_48_738Z-debug-0.log

Did you try recovering your dependencies?

Default installation with the only change being typescript version in package.json

Which terms did you search for in User Guide?

typescript

Environment

Environment Info:

current version of create-react-app: 5.0.1
running from /home/juha/.npm/_npx/c67e74de0542c87c/node_modules/create-react-app

System:
OS: Linux 4.15 Ubuntu 18.04.5 LTS (Bionic Beaver)
CPU: (1) x64 Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
Binaries:
Node: 16.15.1 - ~/.nvm/versions/node/v16.15.1/bin/node
Yarn: Not Found
npm: 8.11.0 - ~/.nvm/versions/node/v16.15.1/bin/npm
Browsers:
Chrome: Not Found
Firefox: 105.0
npmPackages:
react: ^18.2.0 => 18.2.0
react-dom: ^18.2.0 => 18.2.0
react-scripts: 5.0.1 => 5.0.1
npmGlobalPackages:
create-react-app: Not Found

Steps to reproduce

Run npx create-react-app frontend --template typescript
Update package.json to use typescript: "^5.0.2"
Run npm install <some package>
Error appears

Expected behavior

npm install would run successfully.

Actual behavior

$ npm i react-router-dom
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: react-scripts@5.0.1
npm ERR! Found: typescript@5.0.2
npm ERR! node_modules/typescript
npm ERR!   peer typescript@">= 2.7" from fork-ts-checker-webpack-plugin@6.5.3
npm ERR!   node_modules/fork-ts-checker-webpack-plugin
npm ERR!     fork-ts-checker-webpack-plugin@"^6.5.0" from react-dev-utils@12.0.1
npm ERR!     node_modules/react-dev-utils
npm ERR!       react-dev-utils@"^12.0.1" from react-scripts@5.0.1
npm ERR!       node_modules/react-scripts
npm ERR!         react-scripts@"5.0.1" from the root project
npm ERR!   peer typescript@">=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta" from tsutils@3.21.0
npm ERR!   node_modules/tsutils
npm ERR!     tsutils@"^3.21.0" from @typescript-eslint/eslint-plugin@5.55.0
npm ERR!     node_modules/@typescript-eslint/eslint-plugin
npm ERR!       @typescript-eslint/eslint-plugin@"^5.5.0" from eslint-config-react-app@7.0.1
npm ERR!       node_modules/eslint-config-react-app
npm ERR!         eslint-config-react-app@"^7.0.1" from react-scripts@5.0.1
npm ERR!         node_modules/react-scripts
npm ERR!       3 more (eslint-config-react-typescript, eslint-plugin-jest, the root project)
npm ERR!     tsutils@"^3.21.0" from @typescript-eslint/type-utils@5.55.0
npm ERR!     node_modules/@typescript-eslint/type-utils
npm ERR!       @typescript-eslint/type-utils@"5.55.0" from @typescript-eslint/eslint-plugin@5.55.0
npm ERR!       node_modules/@typescript-eslint/eslint-plugin
npm ERR!         @typescript-eslint/eslint-plugin@"^5.5.0" from eslint-config-react-app@7.0.1
npm ERR!         node_modules/eslint-config-react-app
npm ERR!         3 more (eslint-config-react-typescript, eslint-plugin-jest, the root project)
npm ERR!     1 more (@typescript-eslint/typescript-estree)
npm ERR!   1 more (the root project)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional typescript@"^3.2.1 || ^4" from react-scripts@5.0.1
npm ERR! node_modules/react-scripts
npm ERR!   react-scripts@"5.0.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: typescript@4.9.5
npm ERR! node_modules/typescript
npm ERR!   peerOptional typescript@"^3.2.1 || ^4" from react-scripts@5.0.1
npm ERR!   node_modules/react-scripts
npm ERR!     react-scripts@"5.0.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /home/juha/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/juha/.npm/_logs/2023-03-19T13_21_48_738Z-debug-0.log

Reproducible demo

Default CRA using npx create-react-app frontend --template typescript
modify package.json to have "typescript": "^5.0.2"
run npm install <any package>

The text was updated successfully, but these errors were encountered:

Gael-Tonnellier · 2023-03-22T13:32:09Z

Same here, think it needs a minor update to accept typescript 5 . ( released a week ago )

Meligy · 2023-03-29T05:39:13Z

Workaround

CRA seems to work fine with TypeScript 5. So, if you need a temporary workaround for the error and happy to continue working with it, you can achieve that by creating a new overrides section in your package.json (if not existing already), and adding the same typescript version in dependences to it.

Example:

craigmcc · 2023-04-03T17:05:54Z

Trying the workaround from @Meligy on a small application (but with 5.0.3 instead of 5.0.2) has the following results:

Build generates a bunch of TypeError: Cannot set property mark of #<Object> which has only a getter warnings, but does not fail the build.
Tests pass.

I am going to test this on a more substantial application as well.

SleighJ · 2023-04-03T19:07:26Z

Experiencing both issues (TypeError: Cannot set property mark of #<Object> which has only a getter & the npm errors when running install)

The TypeError doesn't keep npm run build from completing, but will prevent the application from building with Docker.

For me, the mentioned work around only suppresses the error when running npm install

KurtGokhan · 2023-04-03T19:32:29Z

I solved the TypeError by adding "fork-ts-checker-webpack-plugin": "^6.5.3" to devDependencies, removing node_modules and lock file and reinstalling. If it doesn't work, make sure the correct version of fork-ts-checker-webpack-plugin is installed by going to the lock file, and remove package manager cache if necessary.

matteatsleftovers · 2023-04-03T21:33:31Z

+1 to @KurtGokhan's TypeError workaround, it worked well for the CRA-based app I'm working on. Following along with the great suggestions in this issue thread, I added some overrides that allowed successful package installation and builds without the TypeError or dependency clashes. I threw in the typescript-estree override because otherwise there was a complaint about unsupported TypeScript version when I linted my app, but YMMV on that addition.

"overrides": {
  "@typescript-eslint/typescript-estree": "^5.57.1",
  "fork-ts-checker-webpack-plugin": "^6.5.3",
  "typescript": "^5.0.3",
},

craigmcc · 2023-04-03T21:49:44Z

I was startled to find a subsequent result after my previous use of @Meligy suggestion. Removing the override failed with react 5.0.2, but succeeded with react 5.0.3! What the heck?

The dependency declarations for react-scripts 5.0.1 did not change, but the resulting behavior certainly did. Without any actual release notes for 5.0.3, it is not at all clear what actually changed that might have caused this.

EDIT: Never mind. Deleting node_modules and reinstalling everything (without the overrides entry) caused the error to reappear. Probably something to do with caching in my IDE.

Tamara-Sennin · 2023-04-04T14:43:12Z

Is there some patch coming to fix this? I updated typescript to v5 and now react-scripts is failing, and we won't put an overrides on our project, that's a workaround not a fix

stefanzero · 2023-04-06T06:39:40Z

This worked for me:

npm install react-router-dom@6 --legacy-peer-deps

arcasoy · 2023-04-12T13:46:22Z

Just bringing this PR to attention to hopefully bump it's visibility and get it approved. This should resolve the issue going forward: #13071

Mihai1iMob · 2023-04-19T19:41:58Z

I just used this override in package.json to make npm i work:

    ...
    "fork-ts-checker-webpack-plugin": "^6.5.3",
    ...
    "typescript": "^5.0.4"
  },
  "overrides": {
    "react-scripts": {
      "typescript": "^5"
    }
  },

bru8787 · 2023-04-22T22:50:03Z

Describe the bug

After npx create-react-app frontend --template typescript, when you update package.json to use "typescript": "^5.0.2",, npm install <any package> fails with this error:

$ npm i react-router-dom
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: react-scripts@5.0.1
npm ERR! Found: typescript@5.0.2
npm ERR! node_modules/typescript
npm ERR!   peer typescript@">= 2.7" from fork-ts-checker-webpack-plugin@6.5.3
npm ERR!   node_modules/fork-ts-checker-webpack-plugin
npm ERR!     fork-ts-checker-webpack-plugin@"^6.5.0" from react-dev-utils@12.0.1
npm ERR!     node_modules/react-dev-utils
npm ERR!       react-dev-utils@"^12.0.1" from react-scripts@5.0.1
npm ERR!       node_modules/react-scripts
npm ERR!         react-scripts@"5.0.1" from the root project
npm ERR!   peer typescript@">=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta" from tsutils@3.21.0
npm ERR!   node_modules/tsutils
npm ERR!     tsutils@"^3.21.0" from @typescript-eslint/eslint-plugin@5.55.0
npm ERR!     node_modules/@typescript-eslint/eslint-plugin
npm ERR!       @typescript-eslint/eslint-plugin@"^5.5.0" from eslint-config-react-app@7.0.1
npm ERR!       node_modules/eslint-config-react-app
npm ERR!         eslint-config-react-app@"^7.0.1" from react-scripts@5.0.1
npm ERR!         node_modules/react-scripts
npm ERR!       3 more (eslint-config-react-typescript, eslint-plugin-jest, the root project)
npm ERR!     tsutils@"^3.21.0" from @typescript-eslint/type-utils@5.55.0
npm ERR!     node_modules/@typescript-eslint/type-utils
npm ERR!       @typescript-eslint/type-utils@"5.55.0" from @typescript-eslint/eslint-plugin@5.55.0
npm ERR!       node_modules/@typescript-eslint/eslint-plugin
npm ERR!         @typescript-eslint/eslint-plugin@"^5.5.0" from eslint-config-react-app@7.0.1
npm ERR!         node_modules/eslint-config-react-app
npm ERR!         3 more (eslint-config-react-typescript, eslint-plugin-jest, the root project)
npm ERR!     1 more (@typescript-eslint/typescript-estree)
npm ERR!   1 more (the root project)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional typescript@"^3.2.1 || ^4" from react-scripts@5.0.1
npm ERR! node_modules/react-scripts
npm ERR!   react-scripts@"5.0.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: typescript@4.9.5
npm ERR! node_modules/typescript
npm ERR!   peerOptional typescript@"^3.2.1 || ^4" from react-scripts@5.0.1
npm ERR!   node_modules/react-scripts
npm ERR!     react-scripts@"5.0.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /home/juha/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/juha/.npm/_logs/2023-03-19T13_21_48_738Z-debug-0.log

Did you try recovering your dependencies?

Default installation with the only change being typescript version in package.json

Which terms did you search for in User Guide?

typescript

Environment

Environment Info:

current version of create-react-app: 5.0.1 running from /home/juha/.npm/_npx/c67e74de0542c87c/node_modules/create-react-app

System: OS: Linux 4.15 Ubuntu 18.04.5 LTS (Bionic Beaver) CPU: (1) x64 Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz Binaries: Node: 16.15.1 - ~/.nvm/versions/node/v16.15.1/bin/node Yarn: Not Found npm: 8.11.0 - ~/.nvm/versions/node/v16.15.1/bin/npm Browsers: Chrome: Not Found Firefox: 105.0 npmPackages: react: ^18.2.0 => 18.2.0 react-dom: ^18.2.0 => 18.2.0 react-scripts: 5.0.1 => 5.0.1 npmGlobalPackages: create-react-app: Not Found

Steps to reproduce

Run npx create-react-app frontend --template typescript
Update package.json to use typescript: "^5.0.2"
Run npm install <some package>
Error appears

Expected behavior

npm install would run successfully.

Actual behavior

$ npm i react-router-dom
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: react-scripts@5.0.1
npm ERR! Found: typescript@5.0.2
npm ERR! node_modules/typescript
npm ERR!   peer typescript@">= 2.7" from fork-ts-checker-webpack-plugin@6.5.3
npm ERR!   node_modules/fork-ts-checker-webpack-plugin
npm ERR!     fork-ts-checker-webpack-plugin@"^6.5.0" from react-dev-utils@12.0.1
npm ERR!     node_modules/react-dev-utils
npm ERR!       react-dev-utils@"^12.0.1" from react-scripts@5.0.1
npm ERR!       node_modules/react-scripts
npm ERR!         react-scripts@"5.0.1" from the root project
npm ERR!   peer typescript@">=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta" from tsutils@3.21.0
npm ERR!   node_modules/tsutils
npm ERR!     tsutils@"^3.21.0" from @typescript-eslint/eslint-plugin@5.55.0
npm ERR!     node_modules/@typescript-eslint/eslint-plugin
npm ERR!       @typescript-eslint/eslint-plugin@"^5.5.0" from eslint-config-react-app@7.0.1
npm ERR!       node_modules/eslint-config-react-app
npm ERR!         eslint-config-react-app@"^7.0.1" from react-scripts@5.0.1
npm ERR!         node_modules/react-scripts
npm ERR!       3 more (eslint-config-react-typescript, eslint-plugin-jest, the root project)
npm ERR!     tsutils@"^3.21.0" from @typescript-eslint/type-utils@5.55.0
npm ERR!     node_modules/@typescript-eslint/type-utils
npm ERR!       @typescript-eslint/type-utils@"5.55.0" from @typescript-eslint/eslint-plugin@5.55.0
npm ERR!       node_modules/@typescript-eslint/eslint-plugin
npm ERR!         @typescript-eslint/eslint-plugin@"^5.5.0" from eslint-config-react-app@7.0.1
npm ERR!         node_modules/eslint-config-react-app
npm ERR!         3 more (eslint-config-react-typescript, eslint-plugin-jest, the root project)
npm ERR!     1 more (@typescript-eslint/typescript-estree)
npm ERR!   1 more (the root project)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional typescript@"^3.2.1 || ^4" from react-scripts@5.0.1
npm ERR! node_modules/react-scripts
npm ERR!   react-scripts@"5.0.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: typescript@4.9.5
npm ERR! node_modules/typescript
npm ERR!   peerOptional typescript@"^3.2.1 || ^4" from react-scripts@5.0.1
npm ERR!   node_modules/react-scripts
npm ERR!     react-scripts@"5.0.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /home/juha/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/juha/.npm/_logs/2023-03-19T13_21_48_738Z-debug-0.log

Reproducible demo

Default CRA using npx create-react-app frontend --template typescript modify package.json to have "typescript": "^5.0.2" run npm install <any package>

Yes , its still an active issue , for me solved removing typescript , running npm i and then install again typescript...

* typescript v5 is not currently supported by react-scripts (see facebook/create-react-app#13080)

until create-react-app bumps their version, see: facebook/create-react-app#13080

* chore(deps): bump axios from 0.24.0 to 1.3.6 * chore(deps): bump eslint from 7.32.0 to 8.39.0 - eslint from 7.32.0 to 8.39.0 - @typescript-eslint/eslint-plugin from 4.33.0 to 5.59.1 - @typescript-eslint/parser from 4.33.0 to 5.59.1 - eslint-plugin-parser from 4.0.0 to 4.2.1 - eslint-config-parser from 8.3.0 to 8.8.1 - correct assignment of license attributes in <meta> * chore(deps): bump i18next and react-i18next - i18next from 22.4.13 to 22.4.15 - react-i18next from 12.2.0 to 12.2.2 * chore(deps): bump ts-node from 10.3.0 to 10.9.1 * chore(deps): bump ts-prune from 0.10.1 to 0.10.3 * chore(deps): bump underscore from 1.13.1 to 1.13.6 * chore(deps): bump rimraf from 3.0.2 to 5.0.0 * chore(deps): bump @types/underscore from 1.11.3 to 1.11.4 * chore(deps): bump react-collapsible from 2.8.4 to 2.8.10 * chore(deps): bump prettier from 2.4.1 to 2.8.8 - add parentheses for `TypeofTypeAnnotation` (prettier/prettier#14458, prettier/prettier#14042) * chore(deps): bump mkdirp from 1.0.4 to 3.0.1 * chore(deps): bump react-to-print from 2.14.0 to 2.14.12 * chore(deps): bump react-icons from 4.3.1 to 4.8.0 * chore(deps): bump gh-pages from 3.2.3 to 4.0.0 note: latest is 5.0.0, but it requires Node>=14 * chore(deps): bump typescript from 4.4.3 to 4.9.5* * typescript v5 is not currently supported by react-scripts (see facebook/create-react-app#13080) * chore(deps): bump google-spreadsheet from 3.1.15 to 3.3.0 * chore(deps): bump depcheck from 1.4.2 to 1.4.3 --------- Co-authored-by: Federico Grandi <fgrandi30@gmail.com>

HassanBharu · 2023-12-08T12:47:33Z

Workaround

CRA seems to work fine with TypeScript 5. So, if you need a temporary workaround for the error and happy to continue working with it, you can achieve that by creating a new overrides section in your package.json (if not existing already), and adding the same typescript version in dependences to it.

Example:

used this as a workaround, pipeline is now building with no error, but I'm guessing there is still not actual fix? in package.json its put dev=true against allot of the modules, will this impact anything else? or any other environments

hokwanhung · 2023-12-15T23:51:42Z

I just used this override in package.json to make npm i work:

    ...
    "fork-ts-checker-webpack-plugin": "^6.5.3",
    ...
    "typescript": "^5.0.4"
  },
  "overrides": {
    "react-scripts": {
      "typescript": "^5"
    }
  },

Currently using this workaround, but I just hope this issue will get solved one day - as it really is not a fix, and consists of risks for projects requiring high stabilities of dependencies.

craigmcc · 2023-12-16T01:50:27Z

It is extremely unlikely that this will ever get officially "fixed".

Create React App is basically dead. Nothing has been updated for over two years now. Even the documentation about it has been migrated to a "legacy" URL:

https://legacy.reactjs.org/docs/create-a-new-react-app.html

The React team recommends using a different toolchain, including (for example) Next.js that has implementation support for React Server Components and Server Actions.

cristianocca · 2023-12-19T23:55:30Z

Looking for an update as well. Sadly, CRA is still widely used and the migration is unjustifiable right now.

… with TypeScript 5. Ref facebook/create-react-app#13080

jvictordev1 · 2024-02-02T13:16:09Z

Workaround

CRA seems to work fine with TypeScript 5. So, if you need a temporary workaround for the error and happy to continue working with it, you can achieve that by creating a new overrides section in your package.json (if not existing already), and adding the same typescript version in dependences to it.

Example:

thanks man this worked!!!!

…-react-app#13080

…ate-react-app#13080

* Remove web vitals check * Add github workflows file for unit test * Add babel dev dependencies to resolve the warning * update node packages * Add tsconfig file * Add eslintignore file * Import necessary packages for converting javascript to typescript * Convert to typescript files * Add overrides to resolve typescript 5.x version based on facebook/create-react-app#13080 * Sync the package lock file with "npm config set legacy-peer-deps false" and "npm i"

* update deps from dependabot alerts * workaround until react-scripts supports TypeScript 5.X facebook/create-react-app#13080

…eact-app#13080

This patch adds the "overrides" section in package.json as a workaround for a TypeScript dependency conflict. For more info, check facebook/create-react-app#13080 It also removes the style-components dependecy, as it's likely to remain unused in this project.

Torniojaws added issue: bug report needs triage labels Mar 22, 2023

omarkohl mentioned this issue Mar 23, 2023

build(deps-dev): bump typescript from 4.9.5 to 5.0.2 in /frontend cleodora-forecasting/cleodora#334

Closed

JapuDCret mentioned this issue Mar 27, 2023

Support for TypeScript 5.x dilanx/craco#503

Open

kennethbigler mentioned this issue Mar 27, 2023

chore(deps): update dependency typescript to v5.0.4 kennethbigler/react-home#950

Merged

1 task

omarkohl mentioned this issue Apr 1, 2023

build(deps-dev): bump typescript from 4.9.5 to 5.0.3 in /frontend cleodora-forecasting/cleodora#368

Closed

jbr mentioned this issue Apr 3, 2023

Bump typescript from 4.9.5 to 5.0.3 in /app divviup/divviup-api#25

Closed

hedgehog1833 mentioned this issue Apr 7, 2023

Bump typescript from 4.9.5 to 5.0.3 MetalDetectorRocks/metal-detector-frontend#603

Closed

marekdedic mentioned this issue Apr 7, 2023

build(deps-dev): bump typescript from 4.9.5 to 5.0.3 in /packages/frontend skaut/poptavky#852

Closed

omarkohl mentioned this issue Apr 15, 2023

build(deps-dev): bump typescript from 4.9.5 to 5.0.4 in /frontend cleodora-forecasting/cleodora#391

Closed

joonashak mentioned this issue Apr 16, 2023

Get rid of npm overrides joonashak/holenav#127

Open

damingerdai mentioned this issue Apr 18, 2023

chore(deps): update dependency typescript to v5 damingerdai/hoteler-web-react#197

Merged

1 task

ocavue mentioned this issue Apr 21, 2023

feat: remove create-react-app example remirror/remirror-examples#43

Merged

FinnBueno mentioned this issue Apr 25, 2023

override typescript version for react-scripts FinnBueno/hexcrawl#32

Merged

lorenzocorallo added a commit to lorenzocorallo/TheTOLProject that referenced this issue Apr 26, 2023

chore(deps): bump typescript from 4.4.3 to 4.9.5*

e0d4c9c

* typescript v5 is not currently supported by react-scripts (see facebook/create-react-app#13080)

shrouxm added a commit to techmatters/terraso-web-client that referenced this issue Apr 26, 2023

workaround: use lower typescript version

cc7d161

until create-react-app bumps their version, see: facebook/create-react-app#13080

matangeorgi mentioned this issue Apr 27, 2023

chore(deps): update latest codux-demos/ducktube#3

Merged

rha6780 mentioned this issue Nov 19, 2023

react 앱 typescript 변경 및 ts 라이브러리 추가 AlgoSolved/AlgoSolved#6

Merged

rickstaa mentioned this issue Nov 20, 2023

[BUG] Dependency updates blocked due to CRA deprication rickstaa/wordeq-2-latexeq#97

Open

AlyssaWang mentioned this issue Dec 15, 2023

FI-2182: Upgrade to TypeScript 5 inferno-framework/inferno-core#418

Merged

Nowe-melancholy mentioned this issue Dec 18, 2023

reactのprojectに後からts入れてみた exchange-wata/pokemon-app-udemy#1

Closed

hokwanhung mentioned this issue Dec 24, 2023

fix: provide overrides for react-json-view with react18 version formio/react-app-starterkit#75

Open

tsmith512 added a commit to tsmith512/vidbin that referenced this issue Jan 15, 2024

Oh. CRA may not be in active development anymore, an there's an issue…

3075048

… with TypeScript 5. Ref facebook/create-react-app#13080

chetbox mentioned this issue Jan 19, 2024

Use react lib v2 clockwork-dog/cra-template-cogs-client#12

Merged

joepegler mentioned this issue Jan 29, 2024

Fix(SMA-574): ESM builds bcnmy/biconomy-client-sdk#393

Merged

14 tasks

Laquinh mentioned this issue Jan 29, 2024

Switch to TypeScript irakur-app/irakur#9

Merged

jmthibault79 mentioned this issue Jan 30, 2024

[risk=low][no ticket] Bump typescript to latest 5.3.3 all-of-us/workbench#8321

Merged

12 tasks

cpeoples added a commit to cpeoples/ecommerce that referenced this issue Feb 12, 2024

Add overrides for nested dependencies until resolved. facebook/create…

bfba68b

…-react-app#13080

yuhueilee added a commit to yuhueilee/wendyfolio that referenced this issue Feb 22, 2024

Add overrides to resolve typescript 5.x version based on facebook/cre…

5e1fb24

…ate-react-app#13080

This was referenced Mar 22, 2024

[Bug]: Unresolvable dependencies from scratch ChrisUser/cra-template-complete-web-app#2

Closed

[Bug]: npm could not resolve dependency ChrisUser/cra-template-complete-web-app#3

Closed

phoenixy1 added a commit to plaid/tiny-quickstart that referenced this issue Mar 25, 2024

add workaround to npm issue facebook/create-react-app#13080

9f64d9d

Alessandro100 mentioned this issue Apr 3, 2024

fix: onboarding config and readme updates for web-app MobilityData/mobility-feed-api#365

Merged

5 tasks

tsuharesu mentioned this issue Apr 11, 2024

RxDb 15.17 and TypeScript Error pubkey/rxdb#5884

Closed

bovrhovn pushed a commit to vrhovnik/azure-sample-cloudtesting that referenced this issue Apr 15, 2024

Update deps from dependabot alerts (microsoft#276)

a2f8a8a

* update deps from dependabot alerts * workaround until react-scripts supports TypeScript 5.X facebook/create-react-app#13080

4sploit added a commit to 4sploit/4sploit.github.io that referenced this issue Apr 20, 2024

Add workaround for react-script support for ts 5.x, facebook/create-r…

ec6fd04

…eact-app#13080

brianmontero18 mentioned this issue Apr 25, 2024

Ts install T00lio/quiz#18

Merged

xbtmatt mentioned this issue Apr 30, 2024

[ECO-1615] Fix peer dependency with react-scripts with override in package.json econia-labs/emojicoin-dot-fun#32

Merged

4 tasks

edelauna mentioned this issue May 30, 2024

build(deps): bump typescript from 4.9.5 to 5.4.5 in /view edelauna/stock-predictor#31

Closed

nimzco mentioned this issue Jun 19, 2024

Eject tech-conferences/confs.tech#639

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

(react-scripts) Support for TypeScript 5.x #13080

(react-scripts) Support for TypeScript 5.x #13080

Torniojaws commented Mar 22, 2023

Gael-Tonnellier commented Mar 22, 2023

Meligy commented Mar 29, 2023

craigmcc commented Apr 3, 2023

SleighJ commented Apr 3, 2023

KurtGokhan commented Apr 3, 2023

matteatsleftovers commented Apr 3, 2023 •

edited

craigmcc commented Apr 3, 2023 •

edited

Tamara-Sennin commented Apr 4, 2023

stefanzero commented Apr 6, 2023

arcasoy commented Apr 12, 2023 •

edited

Mihai1iMob commented Apr 19, 2023 •

edited

bru8787 commented Apr 22, 2023

Describe the bug

Did you try recovering your dependencies?

Which terms did you search for in User Guide?

Environment

Steps to reproduce

Expected behavior

Actual behavior

Reproducible demo

HassanBharu commented Dec 8, 2023

Workaround

hokwanhung commented Dec 15, 2023 •

edited

craigmcc commented Dec 16, 2023

cristianocca commented Dec 19, 2023

jvictordev1 commented Feb 2, 2024

Workaround

(react-scripts) Support for TypeScript 5.x #13080

(react-scripts) Support for TypeScript 5.x #13080

Comments

Torniojaws commented Mar 22, 2023

Describe the bug

Did you try recovering your dependencies?

Which terms did you search for in User Guide?

Environment

Steps to reproduce

Expected behavior

Actual behavior

Reproducible demo

Gael-Tonnellier commented Mar 22, 2023

Meligy commented Mar 29, 2023

Workaround

craigmcc commented Apr 3, 2023

SleighJ commented Apr 3, 2023

KurtGokhan commented Apr 3, 2023

matteatsleftovers commented Apr 3, 2023 • edited

craigmcc commented Apr 3, 2023 • edited

Tamara-Sennin commented Apr 4, 2023

stefanzero commented Apr 6, 2023

arcasoy commented Apr 12, 2023 • edited

Mihai1iMob commented Apr 19, 2023 • edited

bru8787 commented Apr 22, 2023

Describe the bug

Did you try recovering your dependencies?

Which terms did you search for in User Guide?

Environment

Steps to reproduce

Expected behavior

Actual behavior

Reproducible demo

HassanBharu commented Dec 8, 2023

Workaround

hokwanhung commented Dec 15, 2023 • edited

craigmcc commented Dec 16, 2023

cristianocca commented Dec 19, 2023

jvictordev1 commented Feb 2, 2024

Workaround

matteatsleftovers commented Apr 3, 2023 •

edited

craigmcc commented Apr 3, 2023 •

edited

arcasoy commented Apr 12, 2023 •

edited

Mihai1iMob commented Apr 19, 2023 •

edited

hokwanhung commented Dec 15, 2023 •

edited