Upgrade to Next.js 14 Best Practices

[wei]

In addition to just bumping the version like in #268, let's also update the project structure to the latest recommended by Next.js (App directory). Let's also explore the use of server components (if applicable).

[KemingHe]

Hello, @wei. Happy to assist you with migrating to using App dir. Good news is that NextJS supports both at the same time so we can do incremental moves. Let me know how you'd like to proceed. I'm very familiar with the process.

Hear from you soon.

[wei]

Hello, @wei. Happy to assist you with migrating to using App dir. Good news is that NextJS supports both at the same time so we can do incremental moves. Let me know how you'd like to proceed. I'm very familiar with the process.

Hear from you soon.

Hey hey @KemingHe awesome! That'd bea lot of help ❤️. Assigning to you for now 😁

[KemingHe]

In addition to just bumping the version like in #268, let's also update the project structure to the latest recommended by Next.js (App directory). Let's also explore the use of server components (if applicable).

Hello @wei, I suggest we split this issue into two sub tasks:

• Bump to Next.js ver.14
• Bump from Page Router to App Rounter

This way, updates are more incremental, and less pressure on the devs to get everything right first and only time. Let me know what you think. ❤️

[wei]

Sure, I will review and merge dependabot's #289 for the version bump since it's backwards compatible.

[wei]

Upgrade to Next.js 14 in #289 has been complete. Pending research on whether App directory, server components, or any other Next 14 features make sense in our project.

[KemingHe]

Honestly, Page Router is fine for Next.js 14, I assume it will take at least 1~2 year until they sunset it. The upside App Router brings to the project are:

1. Eliminates manual routing, structure/flexibility tradeoff (though more beginner-friendly),
2. Centralized src, api, components code management, easier to refactor, especially with aliasing,

and that's about it. The client/server declaration can just be hard-coded into each page.

All in all, if you want new features over slightly better and future-proofing code, I recommend shelving this util nearing Next ver 15 release.

Let me know what you think: @wei

[wei]

Thanks for the insight. Sounds like a plan. 👍