-
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seeking testers! Confirm that the version on master
works so we can publish a new version
#135
Comments
I just tested, it's working |
I tested |
I've just tested, it's working fine. |
I have been using the |
Right @jamesorlakin! The issue was because of #140. I cancel the changes of the PR (locally) and it seems to work as expected everywhere, but of course we can't have multiple project as it was the purpose of the PR. Basically we remove And it's working but it doesn't solve #140. |
@divlo I can confirm that #126 (comment) is fixed for me on |
Thanks to @divlo's efforts in #132, this extension has been massively updated for the latest version of TypeScript and it now passes the
ts-standard
linter.Since the changes were quite large, before we put out a new release, I'd like at least 5 VSCode users to run the code on
master
and report no problems.If you'd like to test it out and confirm it works for your use case, then please follow these steps:
npm install
npm run package
to build a .vsix filecode --install-extension vscode-standardjs.vsix
If everything works for you, post a comment here indicating it worked for you.
The text was updated successfully, but these errors were encountered: