ecronix/react-most-wanted

resolving dependency issues

Closed this issue · 1 comments

clean install:
npx create-react-app my-app --template material-ui
then when the install gets to installing template dependencies:

nstalling template dependencies using npm...
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: react-most-test@0.1.0
npm ERR! Found: react@17.0.1
npm ERR! node_modules/react
npm ERR!   react@"17.x" from the root project
npm ERR!   peer react@"17.x" from base-shell@1.2.18
npm ERR!   node_modules/base-shell
npm ERR!     base-shell@"1.x" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"16.x" from a2hs@1.1.4
npm ERR! node_modules/a2hs
npm ERR!   peer a2hs@"1.x" from base-shell@1.2.18
npm ERR!   node_modules/base-shell
npm ERR!     base-shell@"1.x" 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.

eresolve-report.txt:

# npm resolution error report

2020-12-04T15:18:14.822Z

While resolving: react-most-test@0.1.0
Found: react@17.0.1
node_modules/react
  react@"17.x" from the root project
  peer react@"17.x" from base-shell@1.2.18
  node_modules/base-shell
    base-shell@"1.x" from the root project

Could not resolve dependency:
peer react@"16.x" from a2hs@1.1.4
node_modules/a2hs
  peer a2hs@"1.x" from base-shell@1.2.18
  node_modules/base-shell
    base-shell@"1.x" from the root project

Fix the upstream dependency conflict, or retry
this command with --force, or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.

Raw JSON explanation object:

{
  "code": "ERESOLVE",
  "current": {
    "name": "react",
    "version": "17.0.1",
    "whileInstalling": {
      "name": "react-most-test",
      "version": "0.1.0",
      "path": "C:\\Dev\\react-most-test"
    },
    "location": "node_modules/react",
    "dependents": [
      {
        "type": "prod",
        "name": "react",
        "spec": "17.x",
        "from": {
          "location": "C:\\Dev\\react-most-test"
        }
      },
      {
        "type": "peer",
        "name": "react",
        "spec": "17.x",
        "from": {
          "name": "base-shell",
          "version": "1.2.18",
          "whileInstalling": {
            "name": "react-most-test",
            "version": "0.1.0",
            "path": "C:\\Dev\\react-most-test"
          },
          "location": "node_modules/base-shell",
          "dependents": [
            {
              "type": "prod",
              "name": "base-shell",
              "spec": "1.x",
              "from": {
                "location": "C:\\Dev\\react-most-test"
              }
            }
          ]
        }
      }
    ]
  },
  "edge": {
    "type": "peer",
    "name": "react",
    "spec": "16.x",
    "error": "INVALID",
    "from": {
      "name": "a2hs",
      "version": "1.1.4",
      "whileInstalling": {
        "name": "react-most-test",
        "version": "0.1.0",
        "path": "C:\\Dev\\react-most-test"
      },
      "location": "node_modules/a2hs",
      "dependents": [
        {
          "type": "peer",
          "name": "a2hs",
          "spec": "1.x",
          "from": {
            "name": "base-shell",
            "version": "1.2.18",
            "whileInstalling": {
              "name": "react-most-test",
              "version": "0.1.0",
              "path": "C:\\Dev\\react-most-test"
            },
            "location": "node_modules/base-shell",
            "dependents": [
              {
                "type": "prod",
                "name": "base-shell",
                "spec": "1.x",
                "from": {
                  "location": "C:\\Dev\\react-most-test"
                }
              }
            ]
          }
        }
      ]
    }
  },
  "peerConflict": null,
  "strictPeerDeps": false,
  "force": false
}

Is there something else I should be doing?
Thanks

Hi @gpearson100 ,

I removed the a2hs package that was causing that error message. It isn't in use anymore. Coould you try it again?