ericelliott/todotasks

Create a script to capture timings and metrics for each implementation

Open

#11 opened on Jan 14, 2015

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (3 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (12 stars)
PR merge metrics
 (PR metrics pending)

Description

For each implementation example, capture a series of metrics and spit out a little report. Can be pretty quick/dirty: - timings for build task (i.e. how long does it take npm run build to finish) - analyze package.json and count required dev dependencies

Possibly output something that can be directly committed to the repo.. maybe .md?

Contributor guide

Research direction
Write a Node.js script that runs 'npm run build' using child process.exec, measures execution time with performance.now(), and reads package.json to count devDependencies. Output a Markdown report with the results. Consider using a library like 'cli table3' for formatting.
Tech stack
javascriptnodejs
Domain
clideveloper experiencetooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Node.jsnpm
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70