refactor: migrate traverse to neotraverse
#1500
Closed
Conversation
This file contains hidden or 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
traverseto neotraversetraverse to neotraverse
|
Thanks for the PR, just tested locally, works fine. I close the PR because there are conflicts, and push the same changes. |
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.
Changes
Removed
traverse&@types/traversein favor ofneotraverse. https://github.com/PuruVJ/neotraverseContext
As part of the ongoing ecosystem cleanup, we are migrating various projects to use lighter/faster packages.
In this case, moving from traverse to neotraverse.
How I've tested my work
npm run test-refactoring