nodejs / nodejs/package-maintenance

Suggestion: Broaden scope to all packages

Open
#73 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

stale?
Dominant language
No language data
Stars
423
Forks
147
PR merge metrics
No merged PRs in 30d

Description

The scope of this initiative thus far is "key packages" in the ecosystem.

I would argue that the huge diversity of packages available for node is in itself key to the ecosystem. Therefore, I feel it'd be ideal if this initiative could widen its scope to trying to put in place systems/assistance which could be applicable to all packages.

Obviously, it'd be an impossible task to make active interventions on thousands of packages, but what I'm trying to suggest is that it'd be useful to bear in mind a wider scope when discussing how to tackle this problem.

An example:

react-loadable is a module which gets 250k weekly downloads, and has been unmaintained for some time including unfixed bugs. 250k evidences a large user base, and judging by the number of open PRs, many motivated would-be contributors - enough I expect to keep the package maintained if they were able to.

But I don't imagine that it's big enough to be considered "key" in the way an express or mocha would.

Only a fraction of node's user-base will use react-loadable. But I would hazard a guess that pretty much every node user depends on some other mid-level package like it. So the experience of using node overall depends not just "key" packages, but a large range of packages.

Perhaps this is already obvious, but I thought I'd make it explicit.

I have a couple of specific suggestions which I'll raise as separate issues as soon as I get a chance, but just wanted to drop this in now in case it's a useful perspective.

Also, just to say, I think this is a great initiative. The burden of maintenance, and the mess of duplicated, abandoned, and half-done packages littering npm that it causes, is the biggest pain point with node. I really hope the community can find some solutions.

Contributor guide

Open the contributing guide

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.

Research direction

No files, tests, or entry points are named. Start by reviewing the initiative's current focus on "key packages" and the discussion around broadening it; done would mean a decided scope and concrete systems or assistance applicable beyond those packages.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.