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

check-package-manager

v0.7.0

Published

Check that you're using the correct package manager

Downloads

1,365

Readme

check-package-manager

Node.js CI

Check that the correct package manager is being used with your project.

To configure the correct package manager, you can use the packageManager property in your package.json file or you can specify it in the cli arguments.

:information_source: This package requires Node >= 18. If you use an older Node version, the cli will exit and print a warning.

Install

npm i check-package-manager -D

:information_source: You can use npx check-package-manager [options] in your preinstall script if you don't want to add it as a dependency.

Usage

check-package-manager [options] [packageManager]

:information_source: Depending on the package manager being used, the preinstall script may get invoked after dependencies are installed.

Arguments

packageManager (optional) - <package manager name>[@<version>]

Options

--info - Print info messages

--debug - Print debug messages

Examples

When using corepack:

{
  "name": "YOUR-PACKAGE-NAME",
  "version": "1.0.0",
  "packageManager": "[email protected]",
  "scripts": {
    "preinstall": "npx check-package-manager"
  }
}

Specify the package manager name and version yourself:

{
  "name": "YOUR-PACKAGE-NAME",
  "version": "1.0.0",
  "scripts": {
    "preinstall": "npx check-package-manager [email protected]"
  }
}

Specify only the package manager name:

{
  "name": "YOUR-PACKAGE-NAME",
  "version": "1.0.0",
  "scripts": {
    "preinstall": "npx check-package-manager yarn"
  }
}

Local development

fnm use
corepack enable
pnpm install
pnpm build