next/link with rewrites works different in preview and local environment

[mrzmyr]

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

https://github.com/mrzmyr/link-to-rewrite-reproduction

To Reproduce

Localhost

https://localhost:3000/example

Preview

https://link-to-rewrite-reproduction-mrzmyr.vercel.app/example

Current vs. Expected behavior

Current

Given the next.config.js

  rewrites: () => [
    {
      source: "/",
      destination: "/en",
    },
  ],

and a link <Link href="/">Go Home</Link>, the redirect on preview deployments sets the slug to ["index"] and to (the correct rewrite) ["en"] on local deployments.

Expected

Given the next.config.js

  rewrites: () => [
    {
      source: "/",
      destination: "/en",
    },
  ],

and a link <Link href="/">Go Home</Link>, the redirect on preview deployments sets the same slug ["en"]on local and preview deployments.

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.4.0: Mon Mar  6 20:59:58 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6020
    Binaries:
      Node: 19.9.0
      npm: 9.6.3
      Yarn: 1.22.19
      pnpm: N/A
    Relevant Packages:
      next: 13.4.20-canary.15
      eslint-config-next: 13.4.19
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.2.2
    Next.js Config:
      output: N/A

Which area(s) are affected? (Select all that apply)

App Router, Routing (next/router, next/navigation, next/link)

Additional context

No response

[jaredwiener]

Having a similar issue.

I have a default route -- similar to app/[id]/page.js -- for user profiles, but also have some rewrites for other pages.

In preview (and not locally) -- it loads the routes in a different order depending on the source of the request.

On the server -- i.e. first load -- it checks the rewrites in next.config.js first.
On the client -- when using <Link> -- it seems to load the default route first.

[nextjs-bot]

This issue has been automatically marked as stale due to two years of inactivity. It will be closed in 7 days unless there’s further input. If you believe this issue is still relevant, please leave a comment or provide updated details. Thank you.

[nextjs-bot]

This issue has been automatically closed due to two years of inactivity. If you’re still experiencing a similar problem or have additional details to share, please open a new issue following our current issue template. Your updated report helps us investigate and address concerns more efficiently. Thank you for your understanding!