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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@kgrid/release-cli

v1.0.4

Published

CLI for building KGrid components and KOs via CircleCI

Readme

KGrid Release CLI

CircleCI GitHub release npm version

This CLI will help you trigger a Release of the KGrid components.

Getting Started

  1. Get a Circle CI a personal api token
  2. npm install -g @kgrid/release-cli
  3. Run export CIRCLECI_TOKEN=#### && kgrid-release

Using the CLI

  1. Choose the component
  2. Adapter is sub module so if Adapter you have to say api or javascript otherwise just press enter
  3. The release version #.#.# for releases #.#.#-rc# for release candidates. This will used to tag the GitHub repository. For maven projects this sets the version
  4. The development version will be #.#.#-SNAPSHOT, used for maven projects can be innored for KO releases.
  5. If it is Pre Release type Y defaults to N

Review the additional [#note]

Will kick off Circle CI build.

  _  ______      _     _   ____      _                        ____ _     ___ 
 | |/ / ___|_ __(_) __| | |  _ \ ___| | ___  __ _ ___  ___   / ___| |   |_ _|
 | ' / |  _| '__| |/ _` | | |_) / _ \ |/ _ \/ _` / __|/ _ \ | |   | |    | | 
 | . \ |_| | |  | | (_| | |  _ <  __/ |  __/ (_| \__ \  __/ | |___| |___ | | 
 |_|\_\____|_|  |_|\__,_| |_| \_\___|_|\___|\__,_|___/\___|  \____|_____|___|
                                                                             
? What KGrid Component are you Releasing? (Use arrow keys)
❯ Activator 
  Adapter 
  Library 
  Play 
  Shelf 

Here is an example of final screen

  _  ______      _     _   ____      _                        ____ _     ___ 
 | |/ / ___|_ __(_) __| | |  _ \ ___| | ___  __ _ ___  ___   / ___| |   |_ _|
 | ' / |  _| '__| |/ _` | | |_) / _ \ |/ _ \/ _` / __|/ _ \ | |   | |    | | 
 | . \ |_| | |  | | (_| | |  _ <  __/ |  __/ (_| \__ \  __/ | |___| |___ | | 
 |_|\_\____|_|  |_|\__,_| |_| \_\___|_|\___|\__,_|___/\___|  \____|_____|___|
                                                                             
? What KGrid Component are you Releasing? Activator
? What branch (e.g. hotfix, feature or master)? master
? What is the Component Module (e.g. adapter-api or javascript-adapter or blank)? 
? What is the Release Version (e.g. 1.0.3)? 1.0.1-rc3
? What is the Development Version (e.g 1.0.4-SNAPSHOT)? 1.0.1-SNAPSHOT
? Is this PreRelease? Yes
Build has started
~/kgrid-config/release/cli $ 

Issues

  • Issues with executing kgrid-release once installed could be based on a few things
    • make sure it is global npm list -g --depth=0
    • run npm bin -g to global bin path.

Notes

  • Component Module is only need when releasing Adapters. The project consists of mmaven submodules and thus requires more information

  • The Demo components release process consists of updating the the GitHub pages. When releasing Demos you really only have to input a Release Version, it will be used to tag the repo.