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

regimen

v0.2.2

Published

Define what can be consumed. A Chai plugin for design systems at The Grid.

Downloads

29

Readme

Regimen Build Status

Define what can be consumed.

A Chai plugin for design systems at The Grid.

Usage

chai = require "chai"
regimen = require "regimen"
chai.use regimen

Blocks

Properties

The following assertions are equivalent, however the latter provides a better error message:

expect(block.cover).to.exist
# AssertionError: expected undefined to exist
expect(block).with.a "cover"
# AssertionError: expected block 123 to have a cover

Again, assertions could be written as follows:

expect(block.cover.orientation).to.equal "portrait"
# AssertionError: expected 'landscape' to equal 'portrait'
expect(block).to.have.a("cover.orientation").equal "portrait"
# AssertionError: expected block 123 to have a cover.orientation equal to 'portrait' but got 'landscape'
expect(block).to.have.a("cover").oriented "portrait"
# AssertionError: expected block 123 to have a cover with 'portrait' orientation but got 'landscape'

However, if the cover were missing the latter provides the most accurate error message:

expect(block.cover.orientation).to.equal "portrait"
# TypeError: Cannot read property 'orientation' of undefined
expect(block).to.have.a("cover.orientation").equal "portrait"
# AssertionError: expected block 123 to have a cover.orientation
expect(block).to.have.a("cover").oriented "portrait"
# AssertionError: expected block 123 to have a cover

The second option should only serve as interim support for future additions in the block structure until custom properties and methods can be added.

Optionals

To specify requirements about optional content, use maybe:

expect(block).to.maybe.have.a("title")?.with.length.lte 20

Types and Subtypes

  expect(block1).to.be.ofType "video"
  expect(block2).to.not.be.ofType "video"
  expect(block1).to.be.subtypeOf "media"
  expect(block2).to.not.be.subtypeOf "media"

Items

Reposts

  expect(item1).to.be.a.repost
  expect(item2).to.not.be.a.repost

Development

npm install
npm test