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

npm-docs

v1.2.2

Published

The place where all things npm are documented

Downloads

55

Readme

docs.npmjs.com

The place where all things npm are documented.

Build Status Code Climate David-DM

Editing Content

All the markdown files can be found in the content directory. Some of these files live here in this repository, others live in other repositories and are imported during the build process. These imported files are ignored by git to prevent people from accidentally editing the wrong files.

HTML Frontmatter for Page Metadata

This site uses html-frontmatter to add metadata to pages.

title

If a file has a title property in its frontmatter, it will be used for the <title> of the rendered HTML page. If title is absent from the frontmatter, the filename (without the .md extension) is used.

order

Pages are sorted alphabetically by default, but the page order per section can be overridden by using a numerical order frontmatter property. It is not necessary to order all pages in a section: Any pages in a section that don't have an order property will be relegated to the end of that section.

Redirects

If you rename or remove a file, add it to lib/redirects.js to keep things from breaking.

Development

Download node at nodejs.org and install it, if you haven't already.

To run the app locally:

npm install
npm run dev

Now you have a server running nodemon at localhost:5000.

The Build Process

The build is run automatically after every npm install and before npm start. Here's an overview of what it does.

  1. Copies npm documentation from ./node_modules/npm/doc to ./content
  2. Walks the content directory collecting markdown files.
  3. Reads the contents of each markdown file.
  4. Parses HTML Frontmatter from the markdown files
  5. Converts markdown to HTML
  6. Writes content.json with HTML content of each file included.

The copied and generated files are ignored for two reasons:

  1. Keeps the git history uncluttered.
  2. Prevents humans from accidentally editing auto-generated files

Webservice

The content.json file is served publicly at /content.json with CORS support, allowing browsers on other domains to fetch all the npm documentation and accompanying metadata with a single HTTP call.

Tests

npm install
npm test

js-standard-style

Deployment

git push origin +master:deploy-staging
git push origin +master:deploy-production

If you get dissed with an "Everything up-to-date" message, make an empty commit and push again:

git commit -avm "emptiness" --allow-empty