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

Migrate from traverse to neotraverse #61

Open
trivikr opened this issue Aug 8, 2024 · 0 comments
Open

Migrate from traverse to neotraverse #61

trivikr opened this issue Aug 8, 2024 · 0 comments

Comments

@trivikr
Copy link

trivikr commented Aug 8, 2024

Is your feature request related to a problem? Please describe.

The Ecosystem Performance was formed in July 2024 to cleanup, speedup, levelup the JavaScript Ecosystem.
Socket Security team wrote a blog post about it https://socket.dev/blog/javascript-community-launches-e18e-initiative-to-improve-ecosystem-performance

On the e18e cleanup channel on Discord, multiple solutions are being discussed. One of them is to replace traverse with neotraverse, which reduces install size by around 3.5 MB and number of dependencies by 65.
For details, check blog post https://puruvj.dev/blog/forking-and-fixing-traverse

The Foxy/foxy-sdk depends on traverse

"traverse": "^0.6.6",

Describe the solution you'd like

Migrate from traverse to neotraverse

There's a codemod available in https://github.com/es-tooling/module-replacements-codemods to migrate from traverse to neotraverse

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

No branches or pull requests

1 participant