Move away from grunt for managing build process
- Dominant language
- JavaScript
- Stars
- 35.8k
- Forks
- 4.1k
- Avg merge
- 2d 26m
- Merged PRs (30d)
- 33
Description
Rationale:
grunt is legacy at this point (last update was 3 years ago)
Grunt, or associated plugins, is the root contributor to many/most of the currently unresolvable dependency vulnerabilities. Whilst these are generally non-exploitable in this context, they are a source of unnecessary noise for system maintenance and contribute to a more general (and unhelpful) impression that "'npm audit' will never be clean".
Another mechanism for managing the build process needs to be found - whether shell scripts or node scripts or another build tool.
Contributor guide
Research direction
Start by locating the existing Grunt configuration, associated plugins, and dependency setup. Compare shell scripts, Node scripts, and other build tools against the current build process and its dependency vulnerabilities. Done means replacing Grunt with an agreed mechanism while preserving the build and reducing the reported dependency noise.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100