`resolve.tsconfigPaths` fallback conflicts with the generated tsconfig
Open
Nobody has claimed this yet.
types / typescript
- Dominant language
- JavaScript
- Stars
- 20.8k
- Forks
- 2.3k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 156
Description
Describe the problem
https://github.com/sveltejs/kit/issues/16468#issuecomment-5041376925
Describe the proposed solution
Skip the warning when the user has opted into resolve.tsconfigPaths. Detection is the awkward part, svelte-kit sync doesn't see the Vite config, so this may need to be part of #16458's restructuring instead.
Alternatives considered
No response
Importance
nice to have
Additional Information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked discussion in issue #16468 and the restructuring proposed in #16458. Trace how svelte-kit sync generates or warns about the tsconfig and how resolve.tsconfigPaths is read from the Vite config. Done means the warning is skipped when that option is enabled without breaking the generated tsconfig behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vite
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100