You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ArnaudBarre
changed the title
fix(create-vite): set types compiler option in tsconfigs
feat(create-vite): set types compiler option in tsconfigs
May 29, 2025
**Why `global.d.ts` instead of `compilerOptions.types` inside `jsconfig.json` or `tsconfig.json`?**
Setting `compilerOptions.types` shuts out all other types not explicitly listed in the configuration. Using triple-slash references keeps the default TypeScript setting of accepting type information from the entire workspace, while also adding `svelte` and `vite/client` type information.
What do you think about removing vite-env.d.ts in favor of types: ["vite/client"]
I personally always used the later because it's one less file and don't use a syntax arcane syntax
Ah, yeah, that makes sense.
I think we should also update this part of the document to move the types field approach up and put the reference one in the ::: details. https://vite.dev/guide/features.html#client-types
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It will be the default in the next
tsc --init, and I think we should do too. See #20131 for impact once the codebase grows.The shared config in the vue template already sets it.
I updated the svelte one to include previous changes (isolatedModules is implied by the bundler mode in the shared config)