refactor: update ts-morph to 24.0 to match TS 5.6.2 #3036
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🦋 Changeset detectedLatest commit: 446dc96 The changes in this PR will be included in the next version bump. This PR includes changesets to release 20 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
astahmer
force-pushed
the
chore/update-ts-56
branch
from
1b539a2 to
c1ea03d
Compare
segunadebayo
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📝 Description
Closes #3027
update ts-morph to v24.0.0 to match TS 5.6.2
https://github.com/dsherret/ts-morph/blob/latest/packages/ts-morph/CHANGELOG.md#2400-2024-10-05
💣 Is this a breaking change (Yes/No):
yes if you were using an incompatible version of TS (outdated or the opposite, a version too high) vs the current ts-morph version used (21.0.0, supporting at least TS until v5.3)
-> this might lead to weird issues like this #3027