I am getting this error while deploying my nextjs app on vercel

Question

warning " > [email protected]" has incorrect peer dependency "react@^16 || ^17".

and this error also:

warning "eslint-config-next > @typescript-eslint/parser > @typescript-eslint/typescript-estree > [email protected]" has unmet peer dependency "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".

I am not getting what to do actually but I am attaching my package.json file here...

{
  "name": "coderzsales",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "next lint"
  },
  "dependencies": {
    "crypto-js": "^4.1.1",
    "jsonwebtoken": "^8.5.1",
    "mongoose": "^6.3.3",
    "next": "12.1.6",
    "react": "18.1.0",
    "react-dom": "18.1.0",
    "react-icons": "^4.3.1",
    "react-toastify": "^9.0.1",
    "react-top-loading-bar": "^2.1.0"
  },
  "devDependencies": {
    "autoprefixer": "^10.4.7",
    "eslint": "8.15.0",
    "eslint-config-next": "12.1.6",
    "postcss": "^8.4.13",
    "tailwindcss": "^3.0.24"
  }
}

I think that I have to make some changes in package.json file but, have no idea what will happen to app after making changes! I have no that much experience!

Bilal Faiz · Accepted Answer · 2023-01-10 07:05:54Z

21

As mentioned in the above answers this error usually indicates that you have a package installed in your project that depends on a specific version of another package, but that required package is not installed in your project or is not the correct version. Since you're getting this error while deploying to vercel, you need to override your install command with npm install --legacy-peer-deps

answered Jan 10, 2023 at 7:05

Bilal Faiz

4394 silver badges7 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Bittu Joshi · Accepted Answer · 2022-07-24 21:05:09Z

2

You can use this command to fix your issue.

npm install --legacy-peer-deps

We get this error in react top loading package because the author of it has made it using older versions of react (v16) and hasn't maintained the peer deps to tell whether the code can run on newer versions of react or not. The command I posted will most probably fix this issue. It worked for me.

answered Jul 24, 2022 at 21:05

Bittu Joshi

6062 gold badges7 silver badges19 bronze badges

Comments

Mytch · Accepted Answer · 2022-05-21 02:15:25Z

0

Just means the library authors haven't updated the peer deps to show that it's ok or not to use that version.

There's a good chance you'll be alright using the --legacy-peer-deps flag with npm i.

I'd be sure the versions are compatible first, since there were a few breaking changes from react 16/17 to react 18.

edited May 21, 2022 at 2:15

answered May 21, 2022 at 2:11

Mytch

4001 gold badge4 silver badges17 bronze badges

3 Comments

God Coderz Over a year ago

I don't got your point! What I supposed to do, for supressing that error?

God Coderz Over a year ago

Is there any solution with yarn? I am using yarn for this project... and now using npm might give another warning!

Mytch Over a year ago

@GodCoderz See --legacy-peer-deps. That will suppress the error, and continue installing. See also nodejs.org/en/blog/npm/peer-dependencies

Collectives™ on Stack Overflow

I am getting this error while deploying my nextjs app on vercel

3 Answers 3

Comments

Comments

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

Comments

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related