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

add-local-binaries-to-path

v1.1.3

Published

Never type ./node_modules/.bin again! Make locally-installed node modules executable by name by adding ./node_modules/.bin to the $PATH

Downloads

301

Readme

add-local-binaries-to-path

Never type ./node_modules/.bin again!

Make locally-installed node modules executable by name by adding ./node_modules/.bin to the $PATH.

Works for bash, fish, and zsh.

Why?

The goal of this is to avoid "works on my machine" problems. You shouldn't really be installing most modules globally. It's best to declare all of your project's dependencies in the package.json file, so npm install will always work for everyone, regardless of what they have installed globally.

Installation

npm i -g add-local-binaries-to-path

A postinstall task looks for these files:

~/.bashrc
~/.bash_profile
~/.config/fish/config.fish
~/.zshrc

For each shell configuration file found, a string is injected into the file that adds .node_modules/.bin to the $PATH environment variable.

For bash and zsh, it looks like this:

export PATH="$PATH:./node_modules/.bin"

For fish, this:

set -gx PATH $PATH ./node_modules/.bin

Usage

Once you've installed this module, you never really need to use it agin. It has done its work. To make sure it's working, try this:

mkdir foo
cd foo
npm init --yes
npm i shrug --save
shrug
which shrug

Dependencies

  • shells: Get a list of all unix shells for which user configuration files exist. Supports bash, zsh, and fish.

License

MIT

Generated by package-json-to-readme