nandorojo
commented
2 years ago can you show the whole error instead of a cropped screenshot? could you copy the stack trace from the console
Closed Niklas-Liljendahl closed 2 years ago
nandorojo
commented
2 years ago can you show the whole error instead of a cropped screenshot? could you copy the stack trace from the console
nandorojo
commented
2 years ago a few questions. are you in a monorepo? do you have multiple versions of react installed?
try running yarn why react
Niklas-Liljendahl
commented
2 years ago Absolutely, here it is:
Niklas-Liljendahl
commented
2 years ago a few questions. are you in a monorepo? do you have multiple versions of react installed?
try running
yarn why react
Niklas-Liljendahl
commented
2 years ago @nandorojo It seems like it's a few different ones from differents packages.
But if I see it correctly it's only 17.0.2 that's installed purposely.
nandorojo
commented
2 years ago Yeah I see. So your version of npm automatically installs peer deps. if you use the npm legacy peer deps feature it should fix it. or, set a resolution of react to 17.0.2 inside or your package.json.
Plainly, you should only use one version. Using yarn would also solve this.
npm i --legacy-peer-depsOr, in your root package.json, add a resolution:
{
"resolutions": { "react": "17.0.2" }
}If you do this, you need to use yarn (or install an npm tool to do it for you). Make sure you set 17.0.2 to whichever version you actually want to use.
Niklas-Liljendahl
commented
2 years ago Yeah I see. So your version of npm automatically installs peer deps. if you use the npm legacy peer deps feature it should fix it. or, set a resolution of react to 17.0.2 inside or your package.json.
Plainly, you should only use one version. Using yarn would also solve this.
I'll try with using Yarn instead!
But when you say set a resolution of react inside the package.json, do you mean specify the version explicitly or are there any other way of "set a resolution of react to 17.0.2"?
Niklas-Liljendahl
commented
2 years ago Managed to get it to work with:
npm i --legacy-peer-deps
Thanks a lot!
Durwinner
commented
1 year ago Keystone requires a higher version of Next.js, specifically version 13.3 or above. If you encounter an error, please make sure to use at least this version. To fix the issue, you can add the following code to your package.json file:
"resolutions": {
"next": "~13.3.0"
}By adding this code, you're specifying a resolution to use Next.js version 13.3.0 or a compatible version. This can help resolve the problem you're facing. Make sure to save the package.json file after making this change.
Not sure this is the correct place to ask, but I have some issues with using Moti when building both to simulator and to real device.
Specs:
The app crashes with an error saying:
It seems to be related to AnimatePresence. When looking into the code it seems like it's coming from:
node_modules/@motify/core/node_modules/react/cjs/react.development.js(Row: 1623)Worth mentioning is that it work for me previously, but I did a clean install of the repo and since then this issue keeps occuring.
Tried what I could think of: