[performance] 200B win opportunity, clsx/lite
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
Description
Summary 💡
There seems to be an opportunity to shave bundle size with https://github.com/lukeed/clsx/releases/tag/v2.1.0
The full version looks bigger by about this amount https://bundlephobia.com/package/clsx@2.1.0.
For the source, we already have https://www.npmjs.com/package/babel-plugin-optimize-clsx that rewrites everything, so maybe the solution could be executed there.
Examples 🌈
No response
Motivation 🔦
No response
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 reviewing how clsx is used and how babel-plugin-optimize-clsx could rewrite those uses; compare the bundle-size impact with clsx v2.1.0 using the linked Bundlephobia reference. Done means reducing the bundle size without changing the existing behavior, with validation of the affected build output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100