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

@mixer/executed-nested-binary

v1.0.1

Published

Executes a node binary from this folder or any parent

Downloads

14

Readme

node-ex

This tool solves a problem with running scripts in (specifically) Lerna monorepos. Your monorepo will probably common tools, but each package might have its own specific tools and versions. The package specific tools will be found in ./packages/foo/node_modules/.bin, and the common packages in ./node_modules/.bin. However, npm scripts in the nested package will only reference the local binaries. Packages like link-parent-bin allow you to override the nested package binaries with the parent, but these prevent the nested package from being able to install and of its own tools.

node-ex is a simple tool which executes a command with all parent node_module/.bin folders placed in the PATH of the command. Your nested binaries, if present, will override the shared binaries.

Usage

npm install -g @mixer/execute-nested-binary

You can run your commands by prefixing them with node-ex:

$ node-ex prettier --help
Usage: prettier [options] [file/glob ...]

You can also pass --where before the binary to print out its location on your hard drive:

$ node-ex --where prettier
/Users/copeet/Github/potatoes/node_modules/.bin