Fresh create-react-app throws warnings on Node 11
See original GitHub issueIs this a bug report?
Yes
Did you try recovering your dependencies?
Yes
Which terms did you search for in User Guide?
Node compatibility, prerequisites, requirements, node support, npm support, npm warnings, node-gyp, fsevents
Environment
System:
OS: macOS 10.14.2
CPU: x64 Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz
Binaries:
Node: 11.10.1 - ~/.nvm/versions/node/v11.10.1/bin/node
npm: 6.7.0 - ~/.nvm/versions/node/v11.10.1/bin/npm
Browsers:
Chrome: 73.0.3683.75
Firefox: 65.0.1
Safari: 12.0.2
npmPackages:
react: Not Found
react-dom: Not Found
react-scripts: Not Found
npmGlobalPackages:
create-react-app: Not Found
Steps to Reproduce
- Run
npx create-react-app new-app
. - Note warnings shown during installation.
Expected Behavior
There should be no warnings
Actual Behavior
Installation: Screen Recording
![Screen Shot 2019-03-15 at 1 43 14 PM](https://user-images.githubusercontent.com/1985888/54461033-a2606100-4728-11e9-851e-74a7eba24a6a.png)
Reinstallation: Screen Recording
Why am I making this issue?
The getting started guide mentions users must have greater than Node 6. With the animated gif showing a perfect installation, the expectation is that the installation process should not throw any warnings.
I’ve managed to reproduce this on two Mac OS Mojave machines and one Windows 10. My OS X is a clean install. On Windows 10, this package is skipped as an optional dependency (from what I’ve read it’s not needed on Windows).
I feel like I am missing something as this problem would otherwise be reported already.
Related:
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:8 (4 by maintainers)
Top Results From Across the Web
My create-react-app is failing to compile due to ESLint error
This issue has been fixed in the react-scipts:"4.0.3" but, the eslint errors present in the project are not converted to warnings by default ......
Read more >How to fix build failures with `create-react-app` in production
Look into your build logs, and find any warnings printed by your build command. Fixing those warnings will make your build succeed again...
Read more >warning create-react-app > tar-pack > tar@2.2.2 - You.com
Installing the latest version of tar will ensure that using create-react-app does not throw any warning, but this doesn't mean that the issue...
Read more >A Fresh Create React App But always compiling with Error
If you have a downgraded version of the node then try updating it to 16 stable build. node -v nvm install "node-version".
Read more >What To Do if create-react-app Doesn't Work
If you really need create-react-app , you might need to reinstall Node and reconfigure your dependencies to ensure you have a fresh start ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I have also these warning on fresh appllication…
npm WARN @typescript-eslint/eslint-plugin@1.13.0 requires a peer of eslint@^5.0.0 but none is installed. You must install peer dependencies yourself. npm WARN @typescript-eslint/parser@1.13.0 requires a peer of eslint@^5.0.0 but none is installed. You must install peer dependencies yourself. npm WARN ts-pnp@1.1.2 requires a peer of typescript@* but none is installed. You must install peer dependencies yourself. npm WARN tsutils@3.17.1 requires a peer of 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 but none is installed. You must install peer dependencies yourself.
Works for me, but since i’m on Linux it doesn’t install
fsevents
which seems to be your issue:Have you tried 10.x or 12.x to see if it solves your problem? Keep in mind 11.x is long dead now.