npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@nodenv/nodenv-default-packages

v1.0.0

Published

Install default packages every time you install a new version of Node

Downloads

5

Readme

nodenv-default-packages

Build Status

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.

Installation

Installing as a nodenv plugin

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

Installing with Homebrew (for OS X users)

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

Usage

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.

default-packages Files

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).

Updating Default Packages

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.

Credits

Forked from Sam Stephenson's rbenv-default-gems by Josh Hagins and modified for nodenv.