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

@netatwork/check-npm-dependencies

v4.0.0

Published

A linter for bundled npm dependencies

Downloads

4

Readme

@netatwork/check-npm-dependencies

A linter for package locks.

Installation

npm i -D @netatwork/check-npm-dependencies

Configuration

// package.json
{
  ...
  "nawCheckNpmDependencies": {
    "extends": "./some-shared-config.json",
    "noDuplicates": [
      "@example/*"
    ],
    "sameVersions": [
      "@example/*",
      [
        "example-a-*",
        "example-b"
      ]
    ]
  }
}
  • nawCheckNpmDependencies <Config> - Can be a path to load the config from or an object with the following options:
    • extends <string> - A path to load a config from to extend.
    • noDuplicates <string[]> - An array of package name patterns to check for duplicates.
      • In the example above, all packages within the @example scope are checked for duplicates.
    • sameVersions <(string | string[])[]> - An array of patterns or pattern groups to ensure that all packages within a group have the same versions.
      • In the example above, all packages within the @example scope are checked for the same version and example-a-* and example-b are checked for the same version.

Usage

# Run via npx:
npx naw-check-npm-dependencies [...args]
// Or add to your package.json:
{
  "scripts": {
    "test": "naw-check-npm-dependencies ..."
  }
}
  • --context | -c <path> - The path at which to look for a package.json and package-lock.json.