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

@tumblbug/style-guide

v0.2.5

Published

Principles, guidelines and assets for designing and building Tumblbug products.

Downloads

115

Readme

Tumblbug Living Style Guide

Principles, guidelines and assets for designing and building Tumblbug products.

Deployment

To reflect changes to production, it is not enough to merge into master. The version field inside package.json must be upgraded according to semver principles. To summarize:

  • If a small change or fix was performed that does not affect backwards compatibility, use npm version patch.
  • If new functionality was added and backward compatibility is ensured, use npm version minor.
  • If changes that may break backward compatibility were introduced, use npm version major.

After running one of these commands, run npm publish to publish the new version. The changes will get propagated into production the next time web-client gets deployed.

Note that you must log into npm using npm login to be able to do this. Ask someone for our login credentials.