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

nobro

v1.0.2

Published

Prevent brothers and sisters from falling to the dark side by robbing their npm-workflow virginity

Downloads

10

Readme

nobro

Simple is that! Shout out to @marak :) - had good times in berlin and thanks for say - anyway. Do you ever had the feeling or felt the downside, that you have to merge a branch of somebody you really like but it annoys you that he wasn't able to pull the last 30 commits in before his PR?

If so. Here is nobro

It check if your buddy is out of sync with master and just interrupts him with a pic of Vader a corresponding sound track and the saying: do ya think, syncing is for pussies?. And thats it. So if your project is tight to a npm workflow you can just sprinkle that in, where you feel comfortable. See usage in the example.

example usage

In the script section of package.json just do the following:

"scripts": {
  "build": "nobro && webpack --debug",
  "stats": "nobro && webpack --profile --json > stats.json",
  "dev": "nobro && NODE_ENV=development NODE_PATH=$NODE_PATH:./src/shared babel-node --harmony .",
  "start": "nobro && NODE_ENV=production NODE_PATH=$NODE_PATH:./src/shared babel-node --harmony .",
  "start:dev": "nobro && NODE_ENV=development NODE_PATH=$NODE_PATH:./src/shared babel-node --harmony .",
  "test": "nobro && NODE_PATH=$NODE_PATH:./src/shared mocha --compilers js:babel-core/register --require babel-polyfill ./test/test_helper.js 'test/**/*_spec.@(js|jsx)'",
  "test:watch": "nobro && npm run test -- --watch",
  "lint": "nobro && eslint --quiet src",
  "postinstall": "nobro && npm run build"
},

If your buddy is behind 20 commits, it would just displays a pic of darth vader, plays imperial march and says something like he can't go on if he wouldn't sync. Thats annoying but can safe hours or even days with merge-conflicting the shit out of your project. :D

alt tag