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

@orieken/saturday-cucumber-indexer

v0.1.0

Published

A CLI tool to index Cucumber feature files for the Saturday framework.

Readme

Cucumber Indexer (Final Project)

This is a tiny TypeScript CLI that scans .feature files and produces a CucumberIndex JSON compatible with the Final backend. It can also POST the generated index to the backend.

Install / Build

  • cd final/tools/cucumber-indexer
  • npm install
  • npm run build

Usage

  • Generate an index JSON from final/tests/features into final/backend/data:

    • node dist/index.js --features ../../tests/features --suiteId demo-ecommerce --out ../../backend/data/cucumber_index.json
  • Optionally POST directly to a running backend:

    • node dist/index.js --features ../../tests/features --suiteId demo-ecommerce --out ../../backend/data/cucumber_index.json --backend http://localhost:8080

CLI Flags

  • --features : Root folder to scan for .feature files. Defaults to final/tests/features based on repo layout.
  • --suiteId : Suite identifier to embed in the index. Default: demo-ecommerce.
  • --out : Output JSON file. Default: final/backend/data/cucumber_index.json based on repo layout.
  • --backend : When provided, the tool will POST the generated index to /api/cucumber/index.

Notes

  • The parser is deliberately simple (keyword-based). For robustness, consider swapping in a real Gherkin parser later.
  • When running with the local dev cluster (final/local-cluster), start the backend first, then run the indexer with --backend http://localhost:8080 to register the suite.