Tree Shaking Support
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5.6k
- Forks
- 696
- Avg merge
- 8m
- Merged PRs (30d)
- 7
Description
I’ve ported most of the tree-shaking implementation from esbuild to a Metro (Babel) plugin and have been running it in production for about a year. Since #632 is closed, I’d like to know Metro’s plans for tree shaking. I’m happy to contribute or upstream my work if that would be useful.
https://github.com/xhsfe/thor-x/blob/main/packages/metro-plugin-tree-shaking/DESIGN.md
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked DESIGN.md and reviewing the issue’s context about Metro’s Babel plugin and the prior tree-shaking issue #632. The issue does not identify Metro files or tests, and completion depends on establishing whether the offered implementation should be upstreamed and what scope Metro wants.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- babel, javascript
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100