grokability / grokability/goodforms-js
Move Uglify from an npm build step to part of the rollup pipeline
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
It seems like it should work pretty well. We can also consider adding some of the stricter compression options, which can squeeze another 10k out of the now 41k JS file. Which, sure, it's already small - but it could be smaller.
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
No files or tests are named. Start by locating the npm build step and Rollup configuration, then trace how the JavaScript bundle is currently minified. Done means Uglify is part of the Rollup pipeline and the resulting bundle remains compressed; stricter compression options are an open consideration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, rollup
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100