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

Turbo loader options type too strict #74336

Open
Netail opened this issue Dec 27, 2024 · 0 comments
Open

Turbo loader options type too strict #74336

Netail opened this issue Dec 27, 2024 · 0 comments
Labels
bug Issue was opened via the bug report template. TypeScript Related to types with Next.js.

Comments

@Netail
Copy link
Contributor

Netail commented Dec 27, 2024

Link to the code that reproduces this issue

https://github.com/Netail/repro-typescript-next-config

To Reproduce

  1. Install dependencies; yarn install
  2. Inspect next.config.ts
  3. Svgr options clash with turbo options type

Current vs. Expected behavior

The turbo loader options type are a bit too strict compared to what's allowed by e.g. the SVGR plugin options

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:03:15 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 22.11.0
  npm: 10.9.0
  Yarn: 1.22.22
  pnpm: 9.6.0
Relevant Packages:
  next: 15.1.3 // Latest available version is detected (15.1.3).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.2
Next.js Config:
  output: N/A

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

TypeScript

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

next dev (local)

Additional context

No response

@Netail Netail added the bug Issue was opened via the bug report template. label Dec 27, 2024
@github-actions github-actions bot added the TypeScript Related to types with Next.js. label Dec 27, 2024
@Netail Netail changed the title Turbo loader options type clashes with possible options type from plugin Turbo loader options type too strict Dec 27, 2024
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. TypeScript Related to types with Next.js.
Projects
None yet
Development

No branches or pull requests

1 participant