Conversation
Member
Author
|
Note, that I can only deploy from a |
bookman25
reviewed
Mar 30, 2017
| "elegant-spinner": "^1.0.1", | ||
| "jest-editor-support": "18.1.0" | ||
| "jest-editor-support": "19.0.2", | ||
| "jest-test-typescript-parser": "18.1.0" |
Collaborator
There was a problem hiding this comment.
Why not the latest version of the parser?
bookman25
reviewed
Mar 30, 2017
| pretty-format "^18.0.0" | ||
|
|
||
| jest-test-typescript-parser@18.1.0: | ||
| version "19.0.2" |
Collaborator
There was a problem hiding this comment.
lol, looks like you got the latest version of the parser, but package.json doesn't have it.
legend1202
pushed a commit
to legend1202/vscode-jest
that referenced
this pull request
Jun 18, 2023
Add back our TypeScript parser
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.
In jestjs/jest#2973 the TypeScript parser was moved into another node module, so we needed to make the choice in which parser we would using inside this extension.
In updating to the latest jest-editor, we needed this or we go no TypeScript support.