feat: neotraverse/legacy; v0.6.14 #756
Merged
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
|
released as |
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.
This is a follow up of #755 which changes the new 'neotraverse' dependency to 'neotraverse/legacy' for cjs modules.
#755 couldn't be merged because of a regression in [email protected] (see npm/cli#7657). 22.5.1 is out and fixes this but it's not picked up by gh action 'actions/setup-node' yet. So as a temporary fix I set v22.5.1 explicitly in the 'node-version' matrix. We'll need to revert it to '22.x' in a future PR.
Thanks @PuruVJ for the fix! Thanks @eXigentCoder for the report in #753.
Closes #755