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

identify-package-manager

v1.0.2

Published

Check the used package manager in a given repository (npm, pnpm, yarn classic, yarn berry)

Downloads

60

Readme

identify-package-manager 📦📦📦📦

Version

Check the used package manager in a given repository (npm, pnpm, yarn classic, yarn berry).

Highlights

  • can be used as classical dependency or as cli/command line tool
  • cli tool can be run in the root of a repository as well as any subfolder (also inside monorepo sub "workspaces" for example) - it will detect the monorepo's root automatically.
  • written in Typescript

CLI

Global install

Via npm:

npm i -g identify-package-manager

Via yarn:

yarn global add identify-package-manager

npx

Instead of a global install you can also use it via npx:

npx identify-package-manager [options]

Usage

After installation you can use it by running the following command inside any given repository.

identify-package-manager [options]

If used without any option the tool will return info about both, the package manager's name and its version, if detectable.

An example output would be the following:

{
    "name": "yarn-berry",
    "version": {
        "simple": "2.0.1",
        "detailed": {
             "major": 2,
             "minor": 0,
             "patch": 1,
        }
    }
}

If you're only interested in the package manager's name, look at the --nameonly option below:

CLI options

| option | explanation | | ------------------- | -------------------------------------------------------------------------------------------------------------------------------- | | -h / --help | Display this package's help + usage info. | | -v / --version | Display this package's version number. | | -n / --nameonly | If set, the cli tool will only return the used package manager's name (npm, yarn-classic, yarn-berry, pnpm or unknown) |

Classical dependency

Install

npm install --save identify-package-manager

Or if you use Yarn:

yarn add identify-package-manager

Usage

import { identifyPackageManager } from "identify-package-manager";

// get name of package manager:
const packageManager = identifyPackageManager(true);
console.log(packageManager);
// ^ might output 'yarn-berry' for instance

// get entire info about package manager:
const packageManagerInfo = identifyPackageManager();
console.log(packageManagerInfo);
// ^ might output the following for instance:
// {
//     "name": "yarn-berry",
//     "version": {
//         "simple": "2.0.1",
//         "detailed": {
//              "major": 2,
//              "minor": 0,
//              "patch": 1,
//         }
//     }
// }