Overview

Changes

• react/framer-motion
• react/emotion-utils
• react/react-query

It means the same thing.

"react": ">=16.8.0 || ^17.0.0 || ^18" === "react": ">=16.8.0"

• SemVer check

What version were you intending to use?

• "react": ">=16.8.0" ?
• "react": "^16.8.0 || ^17.0.0 || ^18" ?

Considering the presence of the || symbols after >=16.8.0, it seems that the intended version was "^16.8.0 || ^17.0.0 || ^18". I have modified the semver to "react": "^16.8.0 || ^17.0.0 || ^18".
If the intention was to specify >=16.8.0, I will modify it to "react": ">=16.8.0".

When using >= in conjunction with ||, it is typically used as follows: link

"engines": {
    "node": "^14.17.0 || ^16.13.0 || >=18.0.0"
  },

📌 react-query

v1 peerDependencies

"peerDependencies": {
    "react": "^16.8.0"
  },

v2 peerDependencies

"peerDependencies": {
    "react": "^16.8.0 || ^17.0.0"
  },

v3 peerDependencies

 "peerDependencies": {
    "react": "^16.8.0 || ^17.0.0 || ^18.0.0"
  },

📌 @emotion/react

v11.9.3

"peerDependencies": {
    "@babel/core": "^7.0.0",
    "react": ">=16.8.0"
}
    

📌 framer-motion

The only unnecessary part was included in the peerDependencies.
At first, I set up peerDependencies correctly.
"However, unnecessary additions were made starting from v3.7
Starting from v7, the minimum React version requirement was updated to v18, and it was indicated correctly."

❗️v6

"peerDependencies": {
    "react": ">=16.8 || ^17.0.0 || ^18.0.0",
    "react-dom": ">=16.8 || ^17.0.0 || ^18.0.0"
}

✅ v7

"peerDependencies": {
    "react": "^18.0.0",
    "react-dom": "^18.0.0"
}

PR Checklist

• I read and included theses actions below

1. I have read the Contributing Guide
2. I have written documents and tests, if needed.