Skip to content

[BUG] npm install is failing in a freshly-cloned repo #178

Description

@hobbsythe6th

Describe the bug
When I recloned my fork repo from development (totally up-to-date btw), cmd threw this:
Github Repos\Candlestick-2> npm install
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: babel-loader@8.4.1
npm warn Found: webpack@5.108.0
npm warn node_modules/webpack
npm warn peer webpack@">=4.43.0 <6.0.0" from @pmmmwh/react-refresh-webpack-plugin@0.5.17
npm warn node_modules/@pmmmwh/react-refresh-webpack-plugin
npm warn @pmmmwh/react-refresh-webpack-plugin@"^0.5.3" from react-scripts@5.0.1
npm warn node_modules/react-scripts
npm warn 17 more (css-loader, css-minimizer-webpack-plugin, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer webpack@">=2" from babel-loader@8.4.1
npm warn node_modules/babel-loader
npm warn babel-loader@"^8.2.3" from react-scripts@5.0.1
npm warn node_modules/react-scripts
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: file-loader@6.2.0
npm warn Found: webpack@5.108.0
npm warn node_modules/webpack
npm warn peer webpack@">=4.43.0 <6.0.0" from @pmmmwh/react-refresh-webpack-plugin@0.5.17
npm warn node_modules/@pmmmwh/react-refresh-webpack-plugin
npm warn @pmmmwh/react-refresh-webpack-plugin@"^0.5.3" from react-scripts@5.0.1
npm warn node_modules/react-scripts
npm warn 17 more (css-loader, css-minimizer-webpack-plugin, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer webpack@"^4.0.0 || ^5.0.0" from file-loader@6.2.0
npm warn node_modules/file-loader
npm warn file-loader@"^6.2.0" from react-scripts@5.0.1
npm warn node_modules/react-scripts
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: react-resize-detector@12.3.0
npm error Found: react@16.14.0
npm error node_modules/react
npm error react@"^16.13.1" from the root project
npm error peer react@">=16.3.0" from @emotion/core@10.3.1
npm error node_modules/@emotion/core
npm error peer @emotion/core@"^10.0.27" from @emotion/styled@10.3.0
npm error node_modules/@emotion/styled
npm error @emotion/styled@"^10.0.12" from console-feed@3.8.0
npm error node_modules/console-feed
npm error console-feed@"^3.8.0" from the root project
npm error peer @emotion/core@"^10.0.28" from @emotion/styled-base@10.3.0
npm error node_modules/@emotion/styled-base
npm error @emotion/styled-base@"^10.3.0" from @emotion/styled@10.3.0
npm error node_modules/@emotion/styled
npm error @emotion/styled@"^10.0.12" from console-feed@3.8.0
npm error node_modules/console-feed
npm error 2 more (console-feed, emotion-theming)
npm error 32 more (@emotion/react, @emotion/styled, @emotion/styled-base, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^18.0.0 || ^19.0.0" from react-resize-detector@12.3.0
npm error node_modules/react-resize-detector
npm error react-resize-detector@"^12.3.0" from the root project
npm error
npm error Conflicting peer dependency: react@19.2.8
npm error node_modules/react
npm error peer react@"^18.0.0 || ^19.0.0" from react-resize-detector@12.3.0
npm error node_modules/react-resize-detector
npm error react-resize-detector@"^12.3.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.

To reproduce
Steps to reproduce the behavior:

  1. Clone a new repo
  2. Run npm install at root
  3. See error

Expected behavior
Correct installation

Device
Lenovo AIO Desktop
Windows 11
VS Code 1.130

Additional context
I was trying to clone a second version of the repo without some (pretty drastic) WIP changes. They're both in the same folder btw. Commit 1a9a291 is the source of this, I think.

Possible fixes
I think updating to React 18 should do it. Not looked into breaking changes though.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions