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

detect-package-manager

v3.0.2

Published

Detect which package manager you're using (yarn or npm)

Downloads

12,378,173

Readme

detect-package-manager

NPM version NPM downloads CircleCI donate

How does this work?

  1. When there's yarn.lock, package-lock.json, pnpm-lock.yaml, or bun.lockb in current working directory, it will skip other operations and directly resolve yarn, npm, pnpm, or bun.
  2. When there's no lockfile found, it checks if yarn, pnpm, or bun command exists. If so, it resolves yarn, pnpm, or bun otherwise npm.
  3. Results are cached.

Install

yarn add detect-package-manager

Usage

const { detect } = require("detect-package-manager");

detect().then((pm) => {
  console.log(pm);
  //=> 'yarn', 'npm', or 'pnpm', 'bun'
});

API

detect([opts])

  • Arguments:
    • opts.cwd: string Optional, defaults to ., the directory to look up yarn.lock, package-lock.json, or pnpm-lock.yaml.
    • opts.includeGlobalBun: boolean Optional, defaults to false, whether to check if bun exists in PATH.
  • Returns: Promise<PM>

It returns a Promise resolving the name of package manager, could be npm, yarn, or pnpm, bun.

getNpmVersion([pm])

  • Arguments:
    • pm: string Optional, defaults to npm, could be npm, yarn, or pnpm, bun
  • Returns: Promise<string>

It returns a Promise resolving the version of npm or the package manager you specified.

clearCache()

  • Returns: void

Clear cache.

Contributing

  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request :D

Author

detect-package-manager © EGOIST, Released under the MIT License. Authored and maintained by EGOIST with help from contributors (list).

github.com/egoist · GitHub @EGOIST · Twitter @_egoistlily