Skip to content

Generated param matcher does not support NodeNext module (resolution) #13280

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

Closed
hyunbinseo opened this issue Jan 7, 2025 · 0 comments · Fixed by #13286
Closed

Generated param matcher does not support NodeNext module (resolution) #13280

hyunbinseo opened this issue Jan 7, 2025 · 0 comments · Fixed by #13286

Comments

@hyunbinseo
Copy link
Contributor

Describe the bug

SvelteKit does use moduleResolution: moduleResolution by default from v2.

However, I had no problems using modules as NodeNext other than this issue.

I hope theses compiler options are supported as well.

// tsconfig.json
{
  "extends": "./.svelte-kit/tsconfig.json",
  "compilerOptions": {
    // ...
    "module": "NodeNext", // added
    "moduleResolution": "NodeNext" // updated
  }
}
// src/routes/fruits/[page=fruit]/+page.ts
export const load = ({ params }) => {
  // before: "apple" | "orange"
  // after: any
  const page = params.page;
};

Reproduction

https://github.com/hyunbinseo/svelte-kit-13279

Logs

No response

System Info

System:
  OS: macOS 15.2
  CPU: (10) arm64 Apple M1 Pro
  Memory: 81.66 MB / 16.00 GB
  Shell: 5.9 - /bin/zsh
Binaries:
  Node: 22.12.0 - ~/.local/state/fnm_multishells/21185_1736236050279/bin/node
  npm: 10.9.0 - ~/.local/state/fnm_multishells/21185_1736236050279/bin/npm
  pnpm: 9.15.2 - ~/.local/state/fnm_multishells/21185_1736236050279/bin/pnpm
Browsers:
  Chrome: 131.0.6778.205
  Edge: 131.0.2903.112
  Safari: 18.2
npmPackages:
  @sveltejs/adapter-auto: ^3.0.0 => 3.3.1 
  @sveltejs/kit: ^2.0.0 => 2.15.1 
  @sveltejs/vite-plugin-svelte: ^4.0.0 => 4.0.4 
  svelte: ^5.0.0 => 5.16.5 
  vite: ^5.4.11 => 5.4.11

Severity

annoyance

Additional Information

No response

@hyunbinseo hyunbinseo changed the title Generated param matcher does not work with NodeNext module (resolution) Generated param matcher does not support NodeNext module (resolution) Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants