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

enforcepm

v0.0.1

Published

Enforce the usage of a package manager within a project

Downloads

245

Readme

enforcepm

Enforce the usage of a single package manager within your project.

Usage

There's no need to install the package. Just create a Git pre-commit hook and put the following command in there:

npx enforcepm <pm>

Where <pm> is the name of the package manager you want to use within your project.
Currently only npm, yarn and pnpm are supported.

Feel free to open an issue requesting the implementation of your preferred package manager, or even better send a PR.

How does it work?

Since, currently, there is no clean way to prevent a package manager from running (see #4895), the approach chosen by enforcepm is to deals with the consequences of using the wrong package manager.

The main problem with using wrong package managers is the generation of lock files, which are redundant and may cause "consistency issues"

enforcepm deletes any staged lock file other than the desired ones. The deletion is meant to take place in a pre-commit hook.

Contribution

Feel free to fill up issues and send pull requests for fixes or features.