Create-react-app: Unmet peer dependency (typescript) when using create-react-app

Created on 20 Mar 2019  路  2Comments  路  Source: facebook/create-react-app

Is this a bug report?

Yes

Did you try recovering your dependencies?

N/A

Which terms did you search for in User Guide?

unmet peer dependency typescript

Environment

Environment:
OS: Windows 10
Node: 10.15.3
Yarn: 1.8.0
npm: 6.9.0
Watchman: Not Found
Xcode: N/A
Android Studio: Version 2.1.0.0 AI-143.2915827

ERROR: package.json not found!

Steps to Reproduce

  1. run command: npx create-react-app my-react-app
    or
  2. run command: npx init react-app my-react-app
    or
  3. run command: npm install -g create-react-app
  4. run command: create-react-app my-react-app

Expected Behavior

Expected to have a successful output and a fully provisioned 'starter' project

Actual Behavior

Process exits unexpectedly with following output:
[3/4] Linking dependencies...
warning "react-scripts > pnp-webpack-plugin > [email protected]" has unmet peer dependency "typescript@*".
[---------------------------------------------------------------------------------------------------------------------------------------------------] 1/2606
Missing dependencies in package.json

image

Reproducible Demo

N/A

underlying tools

Most helpful comment

@heyimalex thanks for the input, indeed it seems to be related to the same issue.

Although in the issue you linked to, they mention Yarn version 1.14 as likely to solve the issue and since that is not available yet, I've found that I was able to solve my issue just by upgrading the version of Yarn to 1.13.0 (initially had Yarn 1.8.0 in my system when facing this issue).

Hope this might be useful to anyone else running into the same issue.

All 2 comments

Looks related to this issue

@heyimalex thanks for the input, indeed it seems to be related to the same issue.

Although in the issue you linked to, they mention Yarn version 1.14 as likely to solve the issue and since that is not available yet, I've found that I was able to solve my issue just by upgrading the version of Yarn to 1.13.0 (initially had Yarn 1.8.0 in my system when facing this issue).

Hope this might be useful to anyone else running into the same issue.

Was this page helpful?
0 / 5 - 0 ratings