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 🙏

© 2026 – Pkg Stats / Ryan Hefner

obby-lib

v0.2.0

Published

We are using _ava_ for testing and _rollup_ for exporting library and handling dependencies for the tiniest package possible.

Readme

Obby lib

We are using ava for testing and rollup for exporting library and handling dependencies for the tiniest package possible.

Setup

git clone https://github.com/Cikito/obby-lib.git
cd obby-lib
nvm use 10.12.00
yarn
yarn build
yarn link

# go to the app
# npm link obby-lib
# meteor has betrayed us and it does not work currently
# go to obby-components
npm link obby-lib

Dev

cd src
touch yourFunctionName.js
touch yourFunctionName.test.js
# set up test do some coding then:
yarn run test

Deploy

yarn run build
# we need to figure out how we are going to deploy this to npm

Development convetions

  • All files go in src folder there are no sub folders
  • A file per lib function.
  • Always have seperate test file per lib function (this is we dev the function localy in this package)
  • Regular function naming convention: <name>.js, <name>.test.js
  • Transformer function naming convention: <TypePassedIn__TypeReturned>.js, <TypePassedIn__TypeReturned>.test.js
  • Any data that needs to be mocked for tests goes in the mocks folder.