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

fortytwojs

v2.0.1

Published

Package to demonstrate CI and publishing to npmjs.

Downloads

8

Readme

FortyTwoJS

An npm package to demonstrate how to test, build and publish to the NPM Registry using CircleCI.

CircleCI

npm version

Prerequisites

Development

Install dependencies (substitute 'npm' if you don't have yarn):

$ npm install

Lint and run tests:

$ npm run lint
$ npm test

Workflow

TL;DR: Use GitHub Flow.

In more detail:

  1. Create a feature branch.
  2. Create and push commits on that branch.
  3. The feature branch will get built on CircleCI with each push.
  4. Update the CHANGELOG with description of changes.
  5. Create a Pull Request on BitBucket.
  6. When the feature PR is merged, master will get built on CircleCI.

Releasing

  1. Update the CHANGELOG to list the new version.

  2. Add files and commit

     $ git add CHANGELOG.md ...
     $ git commit -m "Release v.X.Y.Z"
  3. Bump the version to the desired level:

     $ npm version (major|minor|patch)
  4. Push

     $ git push origin master --tags

The new version will get built in CircleCI and pushed to the NPM Registry.

Installing

To install and use it in another project:

$ npm install fortytwojs

License

This code is licensed and distributed under the terms of the MIT License (see LICENSE).