-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
docs: link tsconfig sections to kit config #14026
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
Conversation
|
This is great! Thank you! If you're up for it, I think it'd also be helpful to include an example in |
Thank you! I didn't even know this was a thing until now. Do you know if the paths passed through this setting should be relative to the location of the generated tsconfig? (I think having the example Ben mentioned would help here) An out-of-scope random thought: wonder if it's worth typing the typescript.config setting so that it's not just |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you!
ooh good point, lemme push a tweak |
I accidentally pushed 9c9bb7e direct to
I don't think so — the utilities for dealing with config files that TypeScript exports use |
Sometimes folks may not be aware that changes to top-level
tsconfig.json
configs such asinclude
will override instead of merge with the generated.svelte-kit/tsconfig.json
viaextends
.This PR links to the
typscript
config option insvelte.config.js
next to other relevant sections to help boost awareness.(no related ticket)
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
Tests
pnpm test
and lint the project withpnpm lint
andpnpm check
Changesets
pnpm changeset
and following the prompts. Changesets that add features should beminor
and those that fix bugs should bepatch
. Please prefix changeset messages withfeat:
,fix:
, orchore:
.Edits