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

lobal

v1.0.2

Published

Use the local version of global npm modules

Downloads

6

Readme

lobal

You have lots of projects on your computer. Some require different versions of global npm modules.

Sick of typing ./node_modules/.bin/gulp to use the local gulp binary?

lobal to the rescue!

# install lobal
$ npm install -g lobal

# add a shim
$ lobal add coffee

# lobal uses the locally installed coffee binary
$ cd ~/project1
~/project1$ npm install [email protected]
~/project1$ coffee -v
CoffeeScript version 1.7.0
~/project1$ cd ../project2$
~/project2$ npm install [email protected]
~/project2$ coffee -v
CoffeeScript version 1.8.1

# lobal will also use the globally installed module if you arent in a project directory
~/project2$ npm install -g [email protected]
~/project2$ cd ~
$ coffee -v
CoffeeScript version 1.6.0

API

lobal add module

Add a shim named module

lobal remove module

Remove a shim named module

lobal exec module

Look for the module binary locally or globally and execute the file.

How it works

The first time you add a shim local will create a .lobal_shims folder in your home folder and add that folder to your PATH by modifying your .bashrc, .bash_profile, or .profile file.

Shims are just tiny shell scripts that are added to the .lobal_shims folder. The shim scripts just run lobal exec passing your module name, ex: lobal exec coffee.

lobal exec then finds your current project based on your cwd and looks for the specified module there. If the module isn't found in the current project lobal checks to see if the module is installed globally. Once it has found a module lobal executes the file using child_process.spawn with stdio set to 'inherit'.