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

Specific route stops working when deployed #12514

Closed
koryphaee opened this issue Jul 28, 2024 · 1 comment
Closed

Specific route stops working when deployed #12514

koryphaee opened this issue Jul 28, 2024 · 1 comment

Comments

@koryphaee
Copy link

Describe the bug

I have 3 routes in my app:

  • /routes/charts/+page.svelte
  • routes//favorites/+page.svelte
  • /routes/[mode]/+page.svelte

Using the vite dev server everything works as expected. Both /charts and /favorites lead to their specific pages and everything else is captured by the slug [mode].

However, when deploying the frontend (using ASP.NET Core in this example) the /charts stops working. Its now also captured by the slug, leading to the wrong page.

Reproduction

I have created repo with a minimal reproducible example here: https://github.com/koryphaee/SvelteBug. It should be very easy to reproduce: just clone and run docker compose up.

Logs

No response

System Info

I made sure that everything is up-to-date:

System:
  OS: Windows 11 10.0.22631
  CPU: (16) x64 AMD Ryzen 7 5800X3D 8-Core Processor
  Memory: 45.22 GB / 63.91 GB
Binaries:
  Node: 21.0.0 - c:\programs\nodejs\node.EXE
  npm: 10.2.0 - c:\programs\nodejs\npm.CMD
Browsers:
  Edge: Chromium (127.0.2651.74)
  Internet Explorer: 11.0.22621.3527
npmPackages:
  @sveltejs/adapter-static: ^3.0.2 => 3.0.2
  @sveltejs/kit: ^2.5.18 => 2.5.18
  @sveltejs/vite-plugin-svelte: ^3.1.1 => 3.1.1
  svelte: ^4.2.18 => 4.2.18
  vite: ^5.3.5 => 5.3.5

Severity

annoyance

Additional Information

No response

@eltigerchino
Copy link
Member

eltigerchino commented Oct 26, 2024

closing as duplicate of #12739 . See #12739 (comment) for a workaround using a matcher to specifically exclude the other routes for the dynamic route.

@eltigerchino eltigerchino closed this as not planned Won't fix, can't repro, duplicate, stale Oct 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants