feat: svelte-check tsgo support with experimental api#3036
Merged
Conversation
🦋 Changeset detectedLatest commit: ae4218c The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
…nto svelte-check-tsapi
accidentally revert a change
…nto svelte-check-tsapi
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This adds a new
--tsgo-experimental-apiflag in svelte-check for tsgo support, without most of the limitations of the current--tsgo. But because this doesn't cache virtual code, it's slightly slower than --tsgo. This flag is considered experimental and might break in the future.In case people are wondering. No, the editor support is still not ready. The FS proxy approach this PR depends on isn't available under the api over LSP.