To automate maintenance of dependency versions in `express-cli.js`

Open
#298 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
express, javascript, nodejs
Domain
cli, tooling

Research direction

Start by reading express-cli.js and the logic that generates the scaffolded package.json, focusing on where dependency names and versions are hard-coded. Determine a maintainable approach for keeping generated dependencies current, including versions that contain vulnerability fixes; done means new scaffolds no longer require manual version updates.

Written by the indexing model from the issue text.

Description

ideas

Right now the generation of the package.json to scaffold with its corresponding dependencies has hard-coded values of the names of the packages to use and its corresponding version.

This implies a manual maintenance of the version of the packages whenever there is a new release. This can be specially critical to not scaffold to users packages with vulnerabilities (which are already fixed in greater versions).

I would like to discuss a solution for this and also, I would be open to participate with my first contribution on this repository if possible :)

Dominant language
JavaScript
Stars
1.9k
Forks
548
No merged PRs in 30d

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.

More from expressjs/generator

All issues in expressjs/generator

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.