Security News
Node.js EOL Versions CVE Dubbed the "Worst CVE of the Year" by Security Experts
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
@nodenv/nodenv-default-packages
Advanced tools
Install default packages every time you install a new version of Node
This nodenv plugin hooks into the nodenv install
command to automatically install npm
packages every time you install a new version of Node.
It requires the node-build
plugin to be installed.
Forked from the excellent rbenv-default-gems
plugin from sstephenson.
Make sure you have the latest nodenv and node-build versions, then run:
git clone https://github.com/nodenv/nodenv-default-packages.git $(nodenv root)/plugins/nodenv-default-packages
Mac OS X users can install nodenv-default-packages with the Homebrew package manager.
This is the recommended method of installation if you installed nodenv with Homebrew.
$ brew install nodenv/nodenv/nodenv-default-packages
Or, if you would like to install the latest development release:
$ brew install --HEAD nodenv/nodenv/nodenv-default-packages
nodenv-default-packages automatically installs the packages listed in the default-packages file(s) file every time you successfully install a new version of Node with nodenv install
.
Specify packages in default-packages
by name, one per line.
You may optionally specify a semver version spec after the name. For example:
grunt-cli
jshint ~2.6.3
csslint >= 0.9.0 < 0.10.0
Blank lines and lines beginning with a #
are ignored.
nodenv-default-packages reads from $(nodenv root)/default-packages
as well as nodenv/default-packages
under all XDG config directories.
The XDG config directories searched are $XDG_CONFIG_HOME
($HOME/.config
if unset/empty) and all colon-separated $XDG_CONFIG_DIRS
(/etc/xdg
if unset/empty).
if you update your $(nodenv root)/default-packages
and want to refresh some or all of your existing node installations you can use commands like this:
nodenv default-packages install 8.8.1 # Reinstall default packages on Node version 8.8.1
nodenv default-packages install --all # Reinstall default packages on _all_ installed Node versions
NOTE: This may take some time.
Forked from Sam Stephenson's rbenv-default-gems by Josh Hagins and modified for nodenv.
FAQs
Install default packages every time you install a new version of Node
The npm package @nodenv/nodenv-default-packages receives a total of 5 weekly downloads. As such, @nodenv/nodenv-default-packages popularity was classified as not popular.
We found that @nodenv/nodenv-default-packages demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.