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

thing-03151991

v0.0.3

Published

Just another library to save you a few lines when doing prototypal inheritance. To tell you the truth, the real purpose of this project is to teach myself how to build and release a tested project with CI to NPM and the library just happened to fall into

Downloads

3

Readme

Thing

Build Status

Just another library to save you a few lines when doing prototypal inheritance. To tell you the truth, the real purpose of this project is to teach myself how to build and release a tested project with CI to NPM and the idea for the library just happened to be on my mind.

Project Setup

npm init
npm install -g grunt-cli
npm install --save-dev grunt
npm install --save-dev karma
npm install --save-dev phantomjs
npm install --save-dev grunt-karma
npm install --save-dev karma-jasmine
npm install --save-dev karma-phantomjs-launcher
npm install --save-dev grunt-contrib-uglify
grunt test

Continuous Integration Setup

Travis CI is a continuous integration service. That means they provide the platform which verifies your code checkins with automated builds. This is a development practice known as continuous integration. The main goal of CI is to smooth the process of code integration in a shared repository by checking every change. This allows developers to catch problems early and thus allow them to develop more rapidly and with greater confidence.

To get started, sign up for the free trial and enable the Travis integration with your Github account. Read the rest of the instructions here.

Publish to NPM

The two fields you definitely need in your package.json file are the author and version fields. If you have a solid package.json, go ahead and register a user account with the NPM registry. You will be publishing the package under this user.

npm adduser

Once you complete account registration, you can check out your user profile on NPM by going to www.npmjs.com/~<USERNAME>. Now, you can publish your NPM package!

npm publish

Note: make sure that the combination of the package name and the version (<name>@<version>) is unique on NPM. You will not be able to publish successfully otherwise.