Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dev mode not working with route rewriting and disabled languageDetection #51713

Closed
1 task done
AIwcom opened this issue Jun 23, 2023 · 2 comments
Closed
1 task done
Labels
bug Issue was opened via the bug report template. Linking and Navigating Related to Next.js linking (e.g., <Link>) and navigation. Pages Router Related to Pages Router. stale The issue has not seen recent activity.

Comments

@AIwcom
Copy link

AIwcom commented Jun 23, 2023

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.5.0: Mon Apr 24 20:52:24 PDT 2023; root:xnu-8796.121.2~5/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.14.2
      npm: 9.5.0
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.4.7
      eslint-config-next: N/A
      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)

Data fetching (gS(S)P, getInitialProps), Internationalization (i18n), Routing (next/router, next/navigation, next/link)

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

https://github.com/AIwcom/next-bug

To Reproduce

  • check out repository
  • run yarn install
  • run yarn dev
  • access localhost:3000
  • click "Test no rewrite" --> new page loads successfully
  • reload page --> page loads
  • go back to "/"
  • click "Test rewrite" --> new page loads successfully
  • reload page --> 404

Describe the Bug

When accessing a route which is rewritten in next.config directly it ends up in a 404 (only in dev mode - yarn build & yarn start works as expected). I experience this behavior since version >13.2.4.

Expected Behavior

I can access the rewritten route directly in dev mode

Which browser are you using? (if relevant)

not relevant

How are you deploying your application? (if relevant)

not relevant

@AIwcom AIwcom added the bug Issue was opened via the bug report template. label Jun 23, 2023
@github-actions github-actions bot added Pages Router Related to Pages Router. Linking and Navigating Related to Next.js linking (e.g., <Link>) and navigation. labels Jun 23, 2023
@nextjs-bot
Copy link
Collaborator

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 nextjs-bot added the stale The issue has not seen recent activity. label Feb 16, 2025
@nextjs-bot
Copy link
Collaborator

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!

@nextjs-bot nextjs-bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue was opened via the bug report template. Linking and Navigating Related to Next.js linking (e.g., <Link>) and navigation. Pages Router Related to Pages Router. stale The issue has not seen recent activity.
Projects
None yet
Development

No branches or pull requests

2 participants