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

@check-run-reporter/cli

v1.13.0

Published

A GitHub action for uploading structured test reports to > [check-run-reporter.com](https://www.check-run-reporter.com).

Downloads

11

Readme

Check Run Reporter CI Integrations (check-run-reporter/integrations)

standard-readme compliant

Check Run Reporter's client library, CLI, and CI integrations.

This is a monorepo (sort of) for Check Run Reporter's client library, CLI, and CI integrations. Instead of maintaining separate test suites (if any tests at all) for each plugin, this repo contains the core TypeScript code as well as CI plugin integration code. As part of the build and release process, each plugin is pushed to the appropriate repository for consumption.

Install

For the various CI integrations, check the READMEs in their respective repos.

For the CLI, download the latest releas. Binaries are available for Linux, macOS, and Windows.

Usage

For the various CI integrations, check the READMEs in their respective repos.

For the CLI, get the most up-to-date documentation by running crr --help.

Examples

Upload test reports produced by jest-junit

JEST_JUNIT_OUTPUT_DIR='reports/junit' \
JEST_JUNIT_ANCESTOR_SEPARATOR=' › ' \
JEST_JUNIT_CLASSNAME='{classname}' \
JEST_JUNIT_INCLUDE_CONSOLE_OUTPUT=true \
JEST_JUNIT_OUTPUT_NAME='jest.xml' \
JEST_JUNIT_SUITE_NAME='Some Label' \
JEST_JUNIT_TITLE='{title}' \
jest --ci --reporters=jest-junit

crr submit \
  --label='Some Label' \
  --report='reports/junit/**/*.xml' \
  --token='<your token>' \
  --sha="$(git rev-parse HEAD)"

Distribute tests across multiple test runners

If you're on the Persistent plan, you can use Check Run Reporter to efficiently distribute your tests across multiple test runners.

crr split prints the names of all the test files that should be run by this node. Specify the --nodeCount and --nodeIndex options to tell Check Run Reporter how many nodes there are and which node this is. Use the --tests option to identify all candidate test files. Any tests that Check Run Reporter has seen before will be evenly distributed while new test will be spread round-robin.

JEST_JUNIT_OUTPUT_DIR='reports/junit' \
JEST_JUNIT_ANCESTOR_SEPARATOR=' › ' \
JEST_JUNIT_CLASSNAME='{classname}' \
JEST_JUNIT_INCLUDE_CONSOLE_OUTPUT=true \
JEST_JUNIT_OUTPUT_NAME='jest.xml' \
JEST_JUNIT_SUITE_NAME='Some Label' \
JEST_JUNIT_TITLE='{title}' \

npx jest $(crr split \
  --label='Unit Tests' \
  --nodeCount=3 \
  --nodeIndex=1 \
  --tests='src/**/*.spec.ts' \
  --token=$CHECK_RUN_REPORTER_TOKEN)

crr submit \
  --label='Some Label' \
  --nodeCount=3 \
  --nodeIndex=1 \
  --report='reports/junit/**/*.xml' \
  --token='<your token>' \
  --sha="$(git rev-parse HEAD)"

Maintainers

Ian Remmel

Contributing

We welcome pull requests, but for anything more than a minor tweak, please create an issue so we can discuss whether the change is the right direction for the project.

License

MIT © Ian Remmel, LLC 2019-2021