Critical i18n Support & Routing Deficiencies in APP ROUTER

mlnima commented 1 year ago

Verify canary release

[X] I verified that the issue exists in the latest Next.js canary release

Provide environment information

Ubuntu 18,20
Windows 10,11
turbo-Repo latest

the current env I am reporting the bug:
Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 18.12.1
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.4.7
      eslint-config-next: 13.4.4
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.0.4

Which area(s) of Next.js are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue or a replay of the bug

Not Published

To Reproduce

Dear Next.js team,

First and foremost, I'd like to extend my gratitude to all the contributors and maintainers of Next.js. The framework has been instrumental for countless developers, myself included.

However, I must express my concerns regarding the latest releases, particularly with the transition from PAGE ROUTER to APP ROUTER. It appears that APP ROUTER has stripped away the i18n support that was inherently available in the PAGE ROUTER. For instance, it was possible to have the root URL ("/") represent the default language in the older version. Attempts to restore this functionality via middleware.ts rewrites or redirects have proven futile.

Describe the Bug

Furthermore, the examples in the repository pertaining to these changes are, unfortunately, more confounding than clarifying. This lack of clear guidance is exasperating, especially when updates seem to prioritize less crucial enhancements over this fundamental functionality.

From discussions within the developer community, it is apparent that I am not alone in this struggle. Numerous projects are at a standstill, hindered by these deficiencies and the absence of requisite features.

Expected Behavior

I respectfully inquire why the APP ROUTER version was released as stable when it is palpably lacking in features that are indispensable for many. It appears more akin to an alpha release than a stable one.

Could you please provide some insights into the rationale behind this decision, and if there are any plans to promptly address these issues?

Thank you for your attention to this matter. Your continuous efforts in advancing this framework are highly valued by the community.

Sincerely,

Which browser are you using? (if relevant)

latest of chrome and many chrome based, firefox, safari ios

How are you deploying your application? (if relevant)

old fasion way using ubuntu, nginx

masterbater commented 1 year ago

Please move this to discussion please this is not a bug and had been discuss a million times. You dont need to migrate to app router until you can follow its new paradigm.

paulvanbrenk commented 1 year ago

It's telling that i18n was not mentioned in the blog post about their priorities.

https://nextjs.org/blog/june-2023-update

vercel / next.js