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

@as-pect/json-reporter

v9.0.0

Published

Json reporter for as-pect

Readme

jtenner/as-pect - @as-pect/json-reporter

Test Coverage Status Changesets

Write your module in AssemblyScript and get blazing fast bootstrapped tests with WebAssembly speeds!

Documentation

To view the documentation, it's located here on the gitbook. If there are any issues with the docs, please feel free to file an issue!

Reporter API

This package writes JSON from the Suite report facts delivered to onReportFinish({ report }). Custom file reporters should prefer the report event callbacks from @as-pect/core and treat onFinish(ctx) as a legacy compatibility callback.

as-pect legacy JSON v1 contract

@as-pect/json-reporter is the as-pect legacy JSON reporter. It is selected by asp --json and intentionally remains separate from the standardized CTRF reporter in @as-pect/ctrf-reporter.

The reporter writes one sibling .json file per test entry. The file root is an array of result objects in execution order.

Passing and failing tests use this field shape:

{
  "group": "math",
  "name": "adds values",
  "ran": true,
  "pass": true,
  "negated": false,
  "runtime": 3,
  "message": null,
  "actual": "3",
  "expected": "3"
}

Failed tests keep the same fields with pass: false, assertion text in message, and reflected assertion strings in actual and expected when present.

Todo results use the same object shape for compatibility:

{
  "group": "math",
  "name": "TODO: handles division",
  "ran": false,
  "pass": null,
  "negated": false,
  "runtime": 0,
  "message": "",
  "actual": null,
  "expected": null
}

Use asp --ctrf or asp --reporter @as-pect/ctrf-reporter when a consumer expects CTRF root fields such as reportFormat, specVersion, and results.

Contributors

To contribute please see CONTRIBUTING.md.

Thanks to @willemneal and @MaxGraey for all their support in making as-pect the best software it can be.

Other Contributors:

Special Thanks

Special thanks to the AssemblyScript team for creating AssemblyScript itself.