Investigate switching from lighthouse CLI to lighthouse Node API

Open
#8 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
18/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
node.js, typescript
Domain
cli

Research direction

No files or tests are named. Start by locating how the Node.js CLI currently invokes Lighthouse, then review the available Lighthouse Node API entry points. Done means the migration scope and acceptance criteria are agreed, and the crawler still gathers performance data for every page.

Written by the indexing model from the issue text.

Description

question

Discussed in a call with @emersonthis

Dominant language
TypeScript
Stars
373
Forks
15
Avg merge
19h 16m
Merged PRs (30d)
23

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudfour/lighthouse-parade

All issues in cloudfour/lighthouse-parade

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.