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

@onereach/get-version-data

v3.1.0

Published

CLI tool to get version data for deploy

Readme

@onereach/get-version-data

CLI tool to get version data for deploy

How to use

For more details on how to use the install and use the tool run:

npx @onereach/get-version-data --help

To get the version info:

npx @onereach/get-version-data --version

Which will return JSON with service version data like this

{
    "service": "@onereach/flow-builder",
    "version": "2.31.6",
    "feature": "master",
    "tools": {
        "deploy-platform": {
            "version": "2.0.177"
        }
    },
    "deploymentTime": "2022-06-15T14:59:32.798Z",
    "git": {
        "branch": "master",
        "bundleTags": [],
        "commitHash": "8531cf8aef3180c48fb7d0779a3dc231d4af95f8",
        "isDirty": false
    },
    "packages": {
        "@onereach/auth-ui-module": "1.5.0",
        "@onereach/ckeditor5-build-full": "1.1.10",
        "@onereach/external-steps-sdk": "0.2.2",
        "@onereach/or-i18n": "0.0.3",
        "@onereach/sdk": "2.0.276",
        "@onereach/service-navigation": "1.1.3",
        "@onereach/time-interpreter": "1.0.18",
        "@onereach/ui": "2.0.218",
        "@onereach/ui-config": "1.0.8",
        "@onereach/ws-client": "1.1.8"
    }
}

You can use it inside shell scripts like this for example:

#!/usr/bin/env bash

set -eo pipefail # exit on error

#...

# example of getting version info into env variable
VERSION_DATA=$(npx @onereach/get-version-data --dir "$PROJECT_DIR" --no-prettify)
echo $VERSION_DATA

# example of creating a file with version info
npx @onereach/get-version-data --dir "$PROJECT_DIR" --output "$PROJECT_DIR/src/version.json"

#...

How to contribute?

When you start working on something that should be added into changelog run:

pnpm changeset add

Choose what type of change is it: patch, minor or major and add summary (will end up being actual line in the changelog)

How to publish package?

Everything is automated, all you need is run:

pnpm release

Version of the package will be set based on changeset files. Then package will be published and tags will be pushed to git