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

zephyr-bridge

v0.1.0

Published

CLI and library helpers that bridge Zephyr Scale test export and Cucumber report publishing workflows.

Downloads

175

Readme

zephyr-bridge

Reusable Node.js package for:

  • fetching Zephyr Scale BDD test scripts and writing .feature files
  • publishing Cucumber JSON execution reports to Zephyr Scale

Install

npm install zephyr-bridge

CLI usage

You can use the single zephyr-bridge command with subcommands, or call the direct binaries.

Unified CLI

zephyr-bridge fetch-tests <baseUrl> <projectKey> <accessToken> [outputDir]
zephyr-bridge publish-report <baseUrl> <projectKey> <accessToken> [htmlReportUrl] [reportDir]

Examples:

zephyr-bridge fetch-tests https://api.zephyrscale.smartbear.com/v2 WMS <token> ./src/test/java/zephyr_features
zephyr-bridge publish-report https://api.zephyrscale.smartbear.com/v2 WMS <token> https://example/reports/latest ./target/reports

Direct CLI commands

Fetch tests

zephyr-fetch-tests <baseUrl> <projectKey> <accessToken> [outputDir]

Example:

zephyr-fetch-tests https://api.zephyrscale.smartbear.com/v2 WMS <token> ./src/test/java/zephyr_features

Publish report

zephyr-publish-report <baseUrl> <projectKey> <accessToken> [htmlReportUrl] [reportDir]

Example:

zephyr-publish-report https://api.zephyrscale.smartbear.com/v2 WMS <token> https://example/reports/latest ./target/reports

Library usage

const { exportBddTestCases, uploadCucumberResults } = require('zephyr-bridge');

await exportBddTestCases({
  baseUrl: 'https://api.zephyrscale.smartbear.com/v2',
  projectKey: 'WMS',
  accessToken: process.env.ZEPHYR_TOKEN,
  outputDir: './src/test/java/zephyr_features'
});

await uploadCucumberResults({
  baseUrl: 'https://api.zephyrscale.smartbear.com/v2',
  projectKey: 'WMS',
  accessToken: process.env.ZEPHYR_TOKEN,
  htmlReportUrl: 'https://example/reports/latest',
  reportDir: './target/reports'
});

Publish to npm

  1. Review package.json and bump version when needed.
  2. Verify the published contents:
npm run pack:check
  1. Login with npm:
npm login
  1. Run tests:
npm test
  1. Publish:
npm publish --access public

If you later switch to a scoped package (for example @your-org/zephyr-bridge), keep --access public.