Next.js Discord

Discord Forum

Upgrading Nextjs version 13 to 14

Unanswered
Kachi posted this in #help-forum
Open in Discord
KachiOP
Hi everyone, my boss wants me to upgrade my nextjs app from version 13 to 14 by also change pages to app. I understand I would need to change the structure of my codebase but I can’t seem to integrate bootstrap like before and use react-redux on the layout.js file. Please how can I get around that?

33 Replies

riský
v13 -> v14 isn't that much... the pages -> app dir is the real change (so the v13 change guides will be basicly just as helpful - aside from not mentioning server actions)
but I can’t seem to integrate bootstrap like before and use react-redux on the layout.js file.
can you give more example on what wen't wrong tho
Dunker
Besides, i don't know if it's time to migrate or not tbh. Looks like needs some more time
@Dunker Besides, i don't know if it's time to migrate or not tbh. Looks like needs some more time
riský
Can you elaborate... When is the best time? I don't think there is a perfect time but nextjs team has said that the current focus is stability and speed, so I don't think that's much to worry about...
Seeing an internal bug, reporting in, waiting for new patch.. idk looks not okay for me
I am not sure but, react team seems like working on a different thing or preparing a major version
@Dunker Besides, i don't know if it's time to migrate or not tbh. Looks like needs some more time
KachiOP
Thank you.

Do you mean nextjs 14 update is not stable yet?
riský
There is a few things that has an issue, but I think they are mostly fixed... Just try and see imo
KachiOP
Ok thank you
@Kachi Thank you. Do you mean nextjs 14 update is not stable yet?
Dunker
Waiting for next patches will be better imo. You can try new features in your side projects
Learning app dir, it's quirks, common patterns takes time after pages dir, so both learning and migration could lead some big issues. Meanwhile you can learn then in few months you can migrate
riský
you are just going to wait forever... there is at least a few issues every version (i know because i see here...), so just try and if it doesn't work go back down a version/back to before
Dunker
I haven't migrated a project without breaking things so far 🙂
riský
yeah i haven't too
i usaly wait a few days but not that long
its just that this server has a wide diference of things...
Dunker
Things require some experience, knowledge and wonder to make success
I answered a lot questions, all had answers in docs
People want things so fast in short time, when things become alpha a lot devs downloading it
And a lot people picking asking here, before diving into its docs or internet
riský
that is very unrelated... yes there are some who want spoonfeeding, but there are many others with genuine questions... and i can say that because i look through all of posts (even if i don't message because idk how to solve)
Dunker
Some devs thinking the reason of their issue is totally next 🙂
riský
once again that may be some but not all... i choose to ignore those ones and focus on ones with actual questions or actual issues
Dunker
Personally I haven't seen a bug or lack at next, neither in my projects or questions I helped
riský
have you looked at ALL the posts... also releases aren't that common rn and only a few are there anyway... but this is getting very offtopic so im out of this
Dunker
Recently I saw a question about "using async in client components", it was really weird cuz none of our solutions including docs didn't work
I don't think this is a problem with next.js architecture, but somehow we couldn't overcome this from standard ways as expected
riský
can we not divert from the point of this thread... chances are OP might get way more confused readning this the nessary
Dunker
Oh yes, we can move this to general tho
I think he solved it's issue tho