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

only-allow-pro

v1.0.2

Published

package.json

Downloads

1

Readme

cli usage

package.json

{
  "scripts": {
    "build": "only-allow node 16 && vite build",
    "preinstall": "only-allow npm 6.x"
  }
}

if current nodejs version is not match 16, vite build will not excuted!

supported names: ["node", "nodejs", "npm", "pnpm", "yarn", "cnpm"]

api usage

const { match } = require("only-allow-pro");

// current nodejs version is match 16 ?
if (!match("node", "16")) {
  console.log("must use nodejs 16 to start current project.");
  process.exit(1);
}

// current package manager is npm && curent package manager verions is 16
if (!match("npm", "6")) {
  console.log("must use npm and version 6.");
  process.exit(1);
}

we can put above judgement in some build config file, because build tool will load this file.

for example:

  • vue-cli-service powered project => vue.config.js
  • vite powered project => vite.config.js
  • ...

why not use only-allow

only-allow is great node module, but it has some limitations.

  • only-allow only support pm check, but not support version check.
  • only-allow only support pm, not support nodejs version check.