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

dev-norms

v2.0.4

Published

Create and maintain developer norms and PR template for your project in your repo.

Downloads

310

Readme

Quickstart

Add developer norms and a PR template to your project by executing:

npx dev-norms create

Manifesto

Sensible defaults are a great way to smoothly kick start a new project. They make life easier in the beginning, but you can always tweak things later on as your needs change. This is true for new packages/libraries/frameworks you download and this is also true for new teams you start or join. Code is written for human consumption, the fact that they can be compiled is a great side effect. Clean code leads to less bugs, less frustration and overall better developer happiness.

Why Do You Need This?

Developer norms are a necessary way to set some ground rules, so your code base can retain some consistency, remain maintainable over the next days, months and years and all developers are on the same page.

Why keep your norms elsewhere, when you can keep them as a living piece of documentation right in your repo.

Usage

There are two main commands create and update.

Create

Run npx dev-norms create to create a starter list of norms in the root of your project, called dev-norms.md. Keep it relevant and update it to suit your needs.

Update

Run npx dev-norms update --path=. command to overwrite your norms with the latest norms.

Install to Project (Optional)

If you want team members to be aware of this tool, make it a part of your package.json file by executing:

npm install --save-dev dev-norms

Contribute New Norms

Feel free to suggest new sensible defaults, by submitting a PR on https://github.com/duluca/dev-norms to update base dev-norms.md.