upgrading a next project from node 14 to 18
Unanswered
keif posted this in #help-forum
keifOP
I’ve done similar migrations in the past - but this one has far more packages that are causing issues (and it uses packages that I may be able to replace with native functionality - like
Is it better to go brute force, to v18, or should I take a gentler approach to say v16, then v18?
(Why v18? Internal design system was moved to v18, this project, an acquired site, could benefit being inline and having some components replaced that could utilize GraphQL for their calls).
Migrating to the app directory seems unnecessary at this time (I’m familiar with it, it works, but that’s a different migration altogether).
query-string)Is it better to go brute force, to v18, or should I take a gentler approach to say v16, then v18?
(Why v18? Internal design system was moved to v18, this project, an acquired site, could benefit being inline and having some components replaced that could utilize GraphQL for their calls).
Migrating to the app directory seems unnecessary at this time (I’m familiar with it, it works, but that’s a different migration altogether).