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

avn

v0.2.4

Published

Automatic Node Version Switching

Downloads

279

Readme

avn

NPM version Build status Code Climate Coverage Status Dependencies devDependencies

Automatic Version Switching for Node.js

Install

npm install -g avn avn-nvm avn-n
avn setup

Now when you cd into a directory with a .node-version file, avn will automatically detect the change and use your installed version manager to switch to that version of node. What goes in your .node-version file? A semver version number corresponding to the version of Node.js that your project uses.

Plugins

avn supports the following version managers:

We don't recommend using all of these tools to manage your versions of node, but feel free to install all of them. They won't conflict with each other.

io.js

Plugins support a consistent syntax in the .node-version file for specifying the use of io.js rather than node. Simply add an iojs prefix. For instance: iojs-1.4 or iojs-v1.4.

Todo List

  • Support switching back to the previous version of node that you were using when you leave a directory.

Pull requests are welcome!

Troubleshooting

If you're having a problem, please cd to the directory where your .node-version file is stored and run (note the double-underscore prefix):

__avn_debug

The contributing page has details about where to report your issue based on the version manager you use.

Also note that the avn setup command will only work with the version of node with which you installed it. If you install and then switch your node version, you'll get an error that avn can't be found. This is okay, but if you need to run the setup command again, simply npm install -g avn to get a new copy for your current node version.

Updating

Simply reinstall via npm & re-run the setup:

npm install -g avn avn-nvm avn-n
avn setup

License

This project is distributed under the MIT license.