jasongin/nvs

[FEATURE REQUEST] default packages

Open

#288 opened on Oct 12, 2023

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

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

Tech stack
javascriptnodejsshell
Domain
developer experienceclitooling
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.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
needs maintainer response
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Node.js knowledgenpm/yarn familiarityshell scripting basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate the nvs codebase to understand how new node versions are installed, specifically the installation script. Look at the nvm default packages implementation for reference. Propose adding a configuration file (e.g., ~/.nvs/default packages) that is read during node version installation, and then install the listed packages globally. No maintainer feedback has been provided on this issue yet.