respect the types config property for svelte files
#341
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The
typesconfig property was originally designed to speed up development, avoiding outputting types when unnecessary. I now have a usecase where I want to publish Svelte files without types to npm, so they can be used in the Svelte REPL.This isn't ideal however, because that means the published package will also lack
.d.tsfor JS files, but for my particular usecase, this semi-broken state seems ok for now. In a perfect world, we'd output.d.tsfiles that work for type-less Svelte, or the REPL would support TS. (https://learn.svelte.dev may eventually?)Also upgrades deps.