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

development-dashboards-docs

v3.3.1

Published

Formidable Open Source Development Dashboards Documentation

Downloads

7

Readme


For an overview of the project structure please refer to the Gatsby documentation - Building with Components

Getting Started

To install and run the documentation site locally:

$ yarn install
$ yarn run develop

Then, open your favorite browser to localhost:8000. GraphiQL runs at localhost:8000/___graphql.

Ready to Deploy :shipit:

Build the site to test locally.

$ yarn run build

Serve the build.

$ yarn run serve

Then, open your favorite browser to localhost:9000 to verify everything looks correct.

Publishing

When publishing, please make sure to install and use [email protected] to preserve file timestamp metadata as it is required for our overall website build and versions subsequent to 5.6.0 intentionally destroy this metadata:

$ npm install -g [email protected]
$ npm --version
5.6.0

To publish to NPM first create version commits.

$ npm version <newversion | major | minor | patch> (see Versioning notes below)

For a reliable systems of releases, development-dashboards-docs should aim for versioning along these lines:

  • Patch: Typos, missing assets, broken styles, very minor copyedits.
  • Minor: Add a new blog post, change styles.
  • Major: Rearchitect how the lander works, remove pages, or something else huge.

Then actually publish

$ npm publish

And push changes back to GitHub:

$ git push && git push --tags