Migration Plan: Converting to App Router

[smrafiz]

Hi @kinngh and contributors,

Thank you for the great work. I’m currently exploring the idea of migrating this project from the Pages Router to the App Router. This would modernize this project and align it with Next.js' current best practices. Any recommended approach for gradually migrating to App Router, also, how about Shopify OAuth, session handling, or middleware?

Thank you.

[kinngh]

1. App Router isn't Nextjs' best practices, it's what's recommended.
2. This has already been answered multiple times - I'm not moving this repo to App router (SSR) and I'll stick to the much stable, and less "Hello I'm Vercel move so we can charge you more" concept and stick to the Pages router.

As far as other things are concerned, most things from the Pages router can be transferred to the App router, under the assumption that you completely understand how SSR works and you're good to go!

Personally, I wouldn't recommend moving to App Router since I'm of the opinion that Server Side React is a terrible idea and you're gonna have a difficult time using Polaris and other libs if you don't fully understand the spec. Besides, @shopify/polaris needs a React 18.* dependency so you can't upgrade to React 19 anyways.

Instead, double down on Pages router, put a Cloudflare Proxy (free) before your Vercel instance and study Polaris Web Components instead.