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

run-by

v1.0.1

Published

Figure out script is run by npm or yarn

Downloads

3

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

sidoshisidoshi

Keywords

Readme

run-by

Build Status contributions welcome HitCount npm npm

Figure out script is run by npm or yarn

Install

npm install --save run-by

Usage

import runBy from 'run-by'

API

isYarn: boolean

True if the script is started with yarn

isNpm: boolean

True if script is started with npm

runner: ?string

It's value will be one of npm, yarn or null depending on how the script has started. If the script is started with node, runner will be null.

runBy(execPath: string): RunBy

It takes the exec_path env, by default is process.env.npm_execpath. Returns isYarn, isNpm and runner depending on the execpath.

License

MIT © Siddharth Doshi