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

@jsspec/format

v0.1.7

Published

Output formatter for jsspec

Downloads

11

Readme

@jsspec/format

npm (scoped) Travis AppVeyor

Default reporter formatters for jsspec.

class MyFormatter {
  static get description() { return 'I write stuff to the screen'; }
  constructor(specRunner){}
}

subscribe to specRunner events:

  specRunner.on('fileStart' (uniqueFileRunReference, fileName) => {});
  specRunner.on('fileEnd' (uniqueFileRunReference, fileName) => {});
  specRunner.on('contextStart' (specRunner, context) => {});
  specRunner.on('contextEnd' (specRunner, context) => {});
  specRunner.on('exampleStart' (specRunner, example) => {});
  specRunner.on('exampleEnd' (specRunner, example) => {});
  specRunner.on('contextLevelFailure', (specRunner, exampleOrContext) => {});
  specRunner.on('runEnd' (specRunner) => {});

context, example and exampleOrContext each respond to the following:

id // [For a conetxt only] a unique name for this context
description // the description supplied
fullDescription // the description, with all context descriptions pre-pended
kind // the class name of the object
base // a uniq name relating to this spec file run
failure // which may be (hopefully) undefined

failure is either an exception, or an exception converted to an object, depending on how JSSpec was run. It will have the following attributes:

constructor.name
stack
message
expected // may be empty
actual // may be empty

Formatters included:

Null

Does nothing. Use with --format null. Can be used as a base class to create other formatters.

Documentation

-fd or --format documentation. Presents a tree of execution results with checks and crosses for example results. A summary of failures are provided at the end.

Dot

-fo or --format dot. Single character output per test. With summary at the end.