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

@bevry/testen

v9.4.0

Published

Run your tests locally against multiple node.js versions

Downloads

32

Readme

@bevry/testen

Run your tests locally against multiple node.js versions

@bevry/testen is a fork of testen which continues maintenance with various improvements and fixes.

Examples

Success

As JSON:

Failure

As JSON:

Usage

Complete API Documentation.

Testen uses nvm behind the scenes for its node.js version management.

Node.js Versions

The CLI will determine which Node.js versions to run your tests again in this order of most preferred first:

  • use the CLI via -n <version> flag (--node is also suitable):
    • testen -n 8.0.0 -n 10
    • testen -n '8 || 10'
    • testen -n '>=8 <=10'
  • use the package.json configuration file via:
    • "testen": { "node": ["8.0.0", 10] }
    • "testen": { "node": "8 || 10" }
    • "testen": { "node": ">=8 <=10" }
  • use the package.json configuration file via:
    • "testen": { "node": "8 || 10" }
    • "testen": { "node": ">=8 <=10" }
  • otherwise, the current, stable, and system versions are used which are resolved by nvm

Command

The CLI will default to npm test as the command that will run for each Node.js version, however the API has no such default. You can customize this via:

  • use the CLI via -- <command>, e.g. testen -- echo hello world
  • use the package.json configuration file via "testen": { "serial": true }

Serial or Parallel

By default tests will run in parallel (multiple at once), to use serial, you can either:

  • use the CLI via -s flag (--serial is also suitable)
  • use the package.json configuration file via "testen": { "serial": true }

JSON Output

By default Testen will output pretty output, to only output the JSON result, you can either:

  • use the CLI via -j flag (--json is also suitable)
  • use the package.json configuration file via "testen": { "json": true }

Other CLI Flags

Refer to testen --help.

API Usage

Testen also provides an API which can be used like so:

const { Versions } = require('@bevry/testen')
async function main() {
    const versions = new Versions([4, 8, 10, 'current', 'stable', 'system'])
    await versions.load()
    await versions.install()
    await versions.test('npm test')
    console.log(versions.success)
}
main()

Complete API documentation is available.

Install

npm

Install Globally

  • Install: npm install --global @bevry/testen
  • Executable: @bevry/testen

Install Locally

  • Install: npm install --save @bevry/testen
  • Executable: npx @bevry/testen
  • Import: import * as pkg from ('@bevry/testen')
  • Require: const pkg = require('@bevry/testen')

Editions

This package is published with the following editions:

  • @bevry/testen/source/index.ts is TypeScript source code with Import for modules
  • @bevry/testen aliases @bevry/testen/edition-es2022-esm/index.js
  • @bevry/testen/edition-es2022-esm/index.js is TypeScript compiled against ES2022 for Node.js 18 || 20 || 21 with Import for modules
  • @bevry/testen/edition-types/index.d.ts is TypeScript compiled Types with Import for modules

History

Discover the release history by heading on over to the HISTORY.md file.

Backers

Code

Discover how to contribute via the CONTRIBUTING.md file.

Authors

Maintainers

Contributors

Finances

Sponsors

  • Andrew Nesbitt — Software engineer and researcher
  • Balsa — We're Balsa, and we're building tools for builders.
  • Codecov — Empower developers with tools to improve code quality and testing.
  • Poonacha Medappa
  • Rob Morris
  • Sentry — Real-time crash reporting for your web apps, mobile apps, and games.
  • Syntax — Syntax Podcast

Donors

License

Unless stated otherwise all works are:

and licensed under: