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

opa2junit

v0.0.5

Published

Tool for converting OPA test results into JUnit test results

Downloads

14

Readme

opa2junit

NodeJS tool for converting OPA test results to JUnit test results

opa2junit -f input.json

Usage

$ npm install -g opa2junit

opa2junit can then be used in a number of different ways. The recommendation for CI/CD processes is to pipe the result in. This will result in the resulting junit file being written to the console.

opa test . | opa2junit

For CLI options, use the -h or --help options

opa2junit --help

To read in from a file rather than the pipe, use the -f or --file parameters. Note that the -f parameter takes precedence over pipes

opa2junit --file results.json

To write the resulting output to a file rather than the console, use the -o or --output parameters

opa test . | opa2junit --output test-results/test.xml

Note that the above parameters can be used together.

opa2junit -f results.json -o test-results/test.xml

By default, if any tests fail, or error, then opa2junit will return a non-zero return code. This can be disabled by using the -s or --safe parameters

opa2junit -f file-with-errors.json -s