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

@khayll/flowdex

v1.1.4

Published

Minimal CLI that prints 'hello ai'

Readme

Flowdex

This developer tool is called Flowdex, whenever "flowdex" is written it should be understood as the tool which is built from this codebase. This is different from tool-usage or external tools or just tools. Those refer to other tools, such as git, Azure Devops, shell commands, etc.

Code for a coding agent. The coding agents main function is to read a ticket (subject to a specific connector) and then work with the code in the current repository (working directory where the tool is run) and make changes to solve that ticket. Ticket may be called a task or item as well.

By default the project has two connectors:

Built-in connectors

  • azure-devops – loads work items from Azure DevOps. It requires an AZURE_DEVOPS_TOKEN and optionally respects AZURE_DEVOPS_PROXY.
  • openai – sends prompts to the OpenAI chat completion API. Configure it with OPENAI_API_KEY and optionally OPENAI_BASE_URL and OPENAI_MODEL.

The CLI automatically uses these connectors unless other modules are provided.

Main workflow

For detailed information about the main workflow, see docs/main-flow.md.

Configuration

Create a .env file with your personal access token. Optionally specify a proxy via AZURE_DEVOPS_PROXY:

AZURE_DEVOPS_TOKEN=<your pat>
#AZURE_DEVOPS_PROXY=http://proxy.example.com:8080

Connector plugins

Flowdex can load custom connectors at runtime. Set the environment variables WORKITEM_CONNECTOR and LLM_CONNECTOR to the module names of your own implementations. Each plugin should export a default factory function that receives an options object and returns a connector instance implementing the WorkItemConnector or LlmConnector interfaces from src/connectors. When not specified, the built in connectors described above are used. A pair of simple example plugins can be found in the plugins/ directory of this repository and the published package. Alongside the echo LLM and dummy work item examples, there is now a chatgpt.ts plugin which demonstrates how to call the OpenAI chat completion API.

Usage

npx @khayll/flowdex              # prints the detected project
npx @khayll/flowdex task <url>   # prints work item JSON
                                 # <url> can be a direct work item link or a backlog link
npx @khayll/flowdex run <url>    # generates a plan using the ticket
npx @khayll/flowdex prompt "<text>" # runs a free-form prompt against the codebase

Development

For detailed development practices and guidelines, see docs/development.md.

Publishing

To release a new patch version and publish it to npm:

npm version patch
npm publish --access public

The version command updates package.json and package-lock.json and triggers the bundle step via the prepare script. The published package now includes the prompts/ directory as well as the plugins/ examples.