react-component / react-component/motion
Tree-shaking
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 178
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Description
Hi!
I don't use CSSMotionList, only CSSMotion. But i noticed that CSSMotionList still gets in the bundle. is this behavior correct? can this be fixed somehow from the library side or is it a problem on my side?
Contributor guide
No contributing guide indexed for this repository
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 reproducing a bundle that imports CSSMotion without CSSMotionList, then inspect how the library exposes those components and how the bundle is produced. Done means establishing whether CSSMotionList is removed when unused, or documenting the behavior and the library-side limitation if it cannot be tree-shaken.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- build-system, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100