Correct, the Pages Router is very much still supported with new improvements being made. The performance improvements in this post apply there. The same APIs and features included in Next.js 1.0 still work today with the Pages Router.

Please take this seriously: stop advising in github issues to switch to App router as a solution to bugs in page router.

It's not an option for large next.js projects, and certainly does not convey what you're saying here.

Can you be more specific on the issue? It’s possible there’s a reason why App Router was recommended in this case.