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

std-pkg

v1.0.2

Published

The Official package.json Standard™ for npm® endorsed fields

Downloads

8

Readme

std-pkg

The Official package.json Standard™ for Npm® endorsed fields†

  • Lazily asserts Correct™ values using getters
  • Strongly typed
  • Includes community standards

This is useful if you're writing tooling around package.json and want to make sure you are following the Official NPM package.json Standard™.

Install

yarn add std-pkg

Usage

const Package = require('std-pkg');
const fs = require('fs');

let pkgPath = '/path/to/package.json';
let pkgContents = fs.readFileSync('/path/to/package.json', 'utf-8');

let pkg = new Package(pkgPath, pkgContents);

// file paths
pkg.filePath;
pkg.dirPath;
pkg.nodeModulesPath;
pkg.nodeModulesBinPath;
pkg.nodeModulesCachePath;

// file contents
pkg.fileContents;
pkg.json;
pkg.indentation;

// essentials
pkg.name;
pkg.version;

// info
pkg.description;
pkg.keywords;
pkg.license;

// links
pkg.homepage;
pkg.bugs;
pkg.repository;

// maintainers
pkg.author;
pkg.contributors;

// files
pkg.files;
pkg.main;
pkg.bin;
pkg.man;
pkg.directories;

// tasks
pkg.scripts;
pkg.config;

// dependencies
pkg.dependencies;
pkg.devDependencies;
pkg.peerDependencies;
pkg.optionalDependencies;
pkg.bundledDependencies;

// system
pkg.engines;
pkg.os;
pkg.cpu;

// publishing
pkg.private;
pkg.publishConfig;

// yarn
pkg.flat;
pkg.resolutions;
pkg.workspaces;

// bundlers
pkg.module;
pkg.browser;
pkg.source;
pkg.sideEffects;

// typescript
pkg.types;

Read index.js and test.js for valid values for each field.


† This is not really a "standard", npm peeps are just being douchebags about anyone ever trying to standardize things because they as a private company would like to retain control which is the same reason npm is not open source.