kentcdodds / kentcdodds/slice-js
Write a data coverage instrumentation tool
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
One of the coolest implications of SliceJS is removing code creates objects and variables which are never actually used in the slice. In those cases we could actually remove the instantiation of those variables and properties. I call this data shaking (maybe it should be called "variable shaking"?
Anyway, as far as I know, there's currently no tool that instruments JavaScript for data coverage, so we will have to build it ourselves. This project could even be a separate effort from SliceJS and have even wider implications itself. Anyone up for the task?
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
The issue names no files, tests, or entry points. Start by reviewing SliceJS and the linked data shaking proposal, then clarify the scope and expected coverage measurements before implementation; done would require a defined JavaScript instrumentation tool and agreed output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100