-
Notifications
You must be signed in to change notification settings - Fork 40
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
Update web-component-analyzer dependency to fix ts5.x support #305
Conversation
This better matches the repo's current formatting
typescript 5.x removed a few deprecated methods, one of which we depended on inside WCA. That has since been fixed over in the WCA repo. This change is to now bump our dependency of WCA so we pull the fix in. Meanwhile, typescript has also been updated to match the same semver as what WCA depends on (otherwise we get type mismatches when passing `SourceFile` objects around).
Weird that the vscode downloader fails on windows with Node >16, but this modernizes the rest of the tests' node versions |
Thanks for your PR - can confirm that using Thanks you! |
yup we still need to publish the new version of the vscode extension, so that will still have the problems i think for now but peter is looking into it so should be up soon great to know the CLI part works though 🙏 |
Sorry it took a bit of extra time, but the VSCode extension has now been
released!
…On Fri, Jun 16, 2023, 4:18 AM James Garbutt ***@***.***> wrote:
yup we still need to publish the new version of the vscode extension, so
that will still have the problems i think for now
but peter is looking into it so should be up soon
great to know the CLI part works though 🙏
—
Reply to this email directly, view it on GitHub
<#305 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAAM65J2QIVVITIG7O4ZOLXLQ6GRANCNFSM6AAAAAAZE4UQQM>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
this should fix the various problems people are having
cc @rictic
FYI i couldn't write an extra test that fails before this change as i'd need to change the repo's typescript to 5.x, and that breaks the build thanks to a mismatch of types
we could just publish a prerelease and test it manually
let me know what you think