Skip to content
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

Merged
merged 9 commits into from
Jun 14, 2023

Conversation

43081j
Copy link
Contributor

@43081j 43081j commented Jun 13, 2023

  • Update WCA
  • Update typescript to match WCA's version

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

rictic and others added 5 commits May 16, 2023 17:53
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).
@rictic
Copy link
Collaborator

rictic commented Jun 14, 2023

Weird that the vscode downloader fails on windows with Node >16, but this modernizes the rest of the tests' node versions

@rictic rictic merged commit 2422d55 into runem:master Jun 14, 2023
@43081j 43081j deleted the ts5-and-wca-fixes branch June 14, 2023 06:46
@artemyarulin
Copy link

Thanks for your PR - can confirm that using "lit-analyzer": "^2.0.0-pre.3", fixes problem with running lit-analyzer as a command line utility. Unfortunately TypeScript plugin and VS code extension doesn't work still, but I assume it will be fixed later.

Thanks you!

@43081j
Copy link
Contributor Author

43081j commented Jun 16, 2023

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 🙏

@rictic
Copy link
Collaborator

rictic commented Jun 17, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants