We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If I try to update the plugin from http://eclipse-update.palantir.com/eclipse-typescript/, the latest available version is:
Eclipse Typescript 1.8.0.v20160504-1733 Mon Jul 11 16:47:47 PDT 2016
Eclipse Typescript 1.8.0.v20160504-1733
Mon Jul 11 16:47:47 PDT 2016
Version 2.1.0 is available since one year ago (911c0cf), could you please update the installation site?
I think this is the cause for a compilation error that I got ("Cannot find name 'HTMLOptionsCollection'"), caused by a Typescript bug which has been fixed in Typescript 2.0 (microsoft/TypeScript#8220); and I am not the only one that got problems: https://marketplace.eclipse.org/comment/4536#comment-4536
The text was updated successfully, but these errors were encountered:
@giovannipessiva Hi, you will have to use my Fork : #353 And build manually. Check readme/contributing. I have not seen sixinli here since 1 year.
Sorry, something went wrong.
Thank you @Rouche, that worked perfectly! My compilation error is solved. I really hope they merge your PR and update the installation site...
No branches or pull requests
If I try to update the plugin from http://eclipse-update.palantir.com/eclipse-typescript/, the latest available version is:
Version 2.1.0 is available since one year ago (911c0cf), could you please update the installation site?
I think this is the cause for a compilation error that I got ("Cannot find name 'HTMLOptionsCollection'"), caused by a Typescript bug which has been fixed in Typescript 2.0 (microsoft/TypeScript#8220); and I am not the only one that got problems: https://marketplace.eclipse.org/comment/4536#comment-4536
The text was updated successfully, but these errors were encountered: