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

cassproject

v5.0.12

Published

Competency and Skills Service

Readme

cass-npm

CaSS NPM is the CaSS Library, published and available on NPM.

Documentation

Documentation for the CaSS Library can be found in the documentation folder:

Getting Started as a user of the library

We're assuming you're coming from the NPM / GitHub space. To see a developer guide, go to https://devs.cassproject.org/

  • npm install --save cassproject

Getting Started as a contributor

The CaSS Library is a library, and as such can only be run self-contained against unit tests.

Dependencies

  • git clone --recurse-submodules -b <branch> https://github.com/cassproject/cass-npm - Get the code.
  • npm i - Install dependencies.

Tests

Running npm test requires Docker.

Release testing

  • npm test - Runs unit tests in docker images against the CaSS 1.5 repositories using supported Node versions (18+) and Cypress against Edge, Chrome and Electron. Takes some time.

Development unit testing

Development unit tests presume you have a CaSS Repository running on localhost:80. You may get one by running docker run -d --name cass-test -p80:80 cassproject/cass:1.5.0

  • npm automocha - Runs mocha unit tests against current Node environment. Will rerun unit tests on-save.
  • npm mocha - Runs mocha unit tests.
  • npm webpack:cypress - Runs unit tests in Cypress against Chrome (headless)
  • npm webpack:cypressEdge - Runs unit tests in Cypress against Edge (headless)
  • npm webpack:cypress:open - Runs unit tests in Cypress in development mode using webpack packaging. Will rerun unit tests on-save.
  • npm browserify:cypress:open - Runs unit tests in Cypress in development mode using browserify packaging. Will rerun unit tests on-save.

Publish checklist

  • npm upgrade --save Review dependencies, autocomplete version numbers to latest versions.
  • Increment version number using npm version --no-git-tag-version <patch|minor|major>. This automatically updates package.json and yuidoc.json.
  • Update changelog using npm run changelog, and review the changes in CHANGELOG.md.
  • npm install
  • npm audit and fix any audit issues. Stop if npm audit --omit=dev has findings.
  • Update CaSS server version if necessary in package.json
  • npm test - Must not fail any tests.
  • npm run webpack:cypressFirefoxHttps See if the firefox test case has changed.
  • Document code coverage output by the previous step.
  • Commit changes to GitHub.
  • Tag release with semantic version from package.json, push tag.
  • npm publish (must be npm logined)

Changelog

See CHANGELOG.md