Fix extension by upgrading vscode #27
Closed
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
Also: * Change command name prefix so it won't conflict if both extensions are installed * Use yarn consistently instead of mix-and-matching npm + yarn
|
Assuming I won't hear back, I released a fix as this extension for now https://marketplace.visualstudio.com/items?itemName=testdouble.vscode-alternate-alternate-file |
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.
I was getting a lot of null/undefined errors when trying to use the extension (after months of happily using it without issue).
I pulled the code down and I wasn't able to do a clean
yarn installbecause the typings file being downloaded in thepostinstallscript was 404'ing. So the only change I made was to runyarn upgrade vscodeand that not only fixed the install issue, but also appears to have fixed the extension for me.4 years is a long time. Please let me know if the project is still maintained and you're willing and able to publish this patch to the vscode store so the extension keeps working. If not, I'm happy to talk about taking it on under the @testdouble org.