-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[dev-tool] codemods compilation errors due to typescript version mismatch #32278
Comments
with `rush add --dev -m -p typescript@~5.7.2` except `dev-tool` due to copmilation error detailed at #32278. Also bump versions in non-rush projects and samples. ***NO_CI***
with `rush add --dev -m -p typescript@~5.7.2` except `dev-tool` due to copmilation error detailed at #32278. Also bump versions in non-rush projects and samples. ***NO_CI***
with `rush add --dev -m -p typescript@~5.7.2` except `dev-tool` due to copmilation error detailed at #32278. Also bump versions in non-rush projects and samples. ***NO_CI*** cosmos: fix new error about implicit `any[]` storage-blob: react to `Buffer` typing change storage-file-datalake test: react to Uint8Array typing change
ts-morph v25 now depends on typescript 5.7.2 However, this could happen again in future updates. Should we
|
@maorleger thoughts? |
hmm I can try to fix the codemods but to be honest my intention was always to:
Thanks to all of @mpodwysocki 's push we are almost all migrated so they should not be long-lived. So I think I lean towards a combination of "skip type checking for the codemods" and "retire the codemods when ESM migration completes" @jeremymeng - do you happen to have a branch with this repro by any chance? Or do I just upgrade to latest typescript and see it fail? I can play around with seeing how easy it would be to fix? |
+1. I don't want us spending a lot of time on things that will be retired soon
@maorleger downgrading ts-morph to previous version (v24)? |
Right, of course... new year's 🧠still warming up 😆 |
Likely due to the usage of
ts-morph
internals in our codemodsThe text was updated successfully, but these errors were encountered: