jasongin/nvs

[FEATURE REQUEST] default packages

Open

#288 opened on Oct 12, 2023

View on GitHub
 (1 comment) (1 reaction) (0 assignees)JavaScript (198 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (2,377 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

I'd like to propose the feature of default packages when a new node version is being added.

For example, I use yarn across all my projects, but I need to explicitly install it for every new node version that nvs adds.

I think having a default-packages file somewhere would solve this problem, like nvm does.

Do you all think that this feature is worth investing a developer-time?

Contributor guide

Research direction
Examine the nvs source code to understand how new Node versions are installed. Study nvm's default packages feature. Then implement a default packages file that gets read during installation.
Tech stack
javascriptnodejs
Domain
clideveloper experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
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.
65