Issues with the update to next 15 with codemod
Answered
Hunting wasp posted this in #help-forum
Hunting waspOP
seeing issues with quite a few dependencies with next 15 after the codemod and updating
for example:
@types/react
override to @rc
. anyone else? Stuff like clerk, resend, drizzle, zustand, framer-motionfor example:
├─┬ framer-motion 11.11.9
│ ├── ✕ unmet peer react@^18.0.0: found 19.0.0-rc-69d4b800-20241021
│ └── ✕ unmet peer react-dom@^18.0.0: found 19.0.0-rc-69d4b800-20241021
Answered by Asian black bear
That's not an issue, those packages just aren't updated to explicitly add that they support React 19 RC.
3 Replies
Asian black bear
That's not an issue, those packages just aren't updated to explicitly add that they support React 19 RC.
Answer
Asian black bear
Library authors will have to update their peer dependencies eventually.
Hunting waspOP
okay sweet, I kinda figured but was a bit worrying - mostly because I was seeing errors due to clerk after upgrading to next 15. Luckily clerk had a v6 codemod that made it work instantly with next 15 as well.
Almost felt too easy... these codemods are a bit crazy
Almost felt too easy... these codemods are a bit crazy