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

@cmi5/requirements

v1.0.0

Published

JSON list of cmi5 specification requirements.

Downloads

195

Readme

@cmi5/requirements

This package is intended to track the requirements of the cmi5 specification in a JSON file. There are two types of requirements in the file--explicit and derived. Explicit requirements are numbered based on their section in the specification followed by an ordered index of where the requirement is positioned in the section. (Note: due to potential changes in the specification over time the index order may not be true to the specification beyond the initial starting point.) Derived requirements are numbered based on the explicit requirement from which they are derived followed by a suffix of (d#).

Install

npm install @cmi5/requirements

Usage

The requirements.json JSON file provides a structure with an object at the top level. That object contains a property for each requirement (and derived requirements) that have as their value an object with a single txt property that is the wording from the specification itself.