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

add-workflow-builder

v0.1.6

Published

Installs the Workflow Builder feature (Builder / Workflows / Execution History) into an existing Imola Kit Pro project.

Readme

add-workflow-builder

Published on npm: npx add-workflow-builder@latest.

Installs the Workflow Builder feature (Builder / Workflows / Execution History) from workflow-builder-component into an existing project. Fully automatic on Imola Kit Pro projects (Vite + React Router variant, TypeScript or JavaScript); on any other stack, use --dump-assets and integrate by hand (or via the companion Skill, which does this adaptation for you) — see ~/.claude/skills/workflow-builder-init/ (a global user skill, like ikp-init — install it there once, use it from any project via /workflow-builder-init).

What it does

  1. Detects the target project (TS vs JS, package manager) and checks whether it's an Imola Kit Pro project.
  2. Copies the feature's 19 component/page files plus the 7 lib/api files (stripping TypeScript for JS targets via esbuild).
  3. Patches src/paths.ts, src/routes/dashboard.tsx, src/config/dashboard.ts, src/components/dashboard/layout/nav-icons.tsx, and src/locales/{en,de,es}/index.ts — all idempotently, safe to re-run.
  4. Merges the required npm dependencies (@dnd-kit/*, recharts) into package.json.
  5. Appends VITE_API_URL to .env/.env.example.
  6. Optionally seeds the shared workflow_builder_backend's required admin user (its auth is a stub — see that repo's README).
  7. Optionally writes a real table list into tables.ts (via --tables), replacing the placeholder — see the companion Skill at ~/.claude/skills/workflow-builder-init/ (a global user skill, like ikp-init — install it there once, use it from any project via /workflow-builder-init) for how to discover a client's real tables and feed them in.

None of the above needs a decision from whoever's running it — the target directory and backend URL default silently. The only interactive prompt is for a Postgres connection string, and only if --seed-db=yes is passed without --database-url.

Usage

npx add-workflow-builder@latest                                    # defaults: cwd, shared backend URL
npx add-workflow-builder@latest --tables='[{"id":"orders","label":"Orders"}]'
npx add-workflow-builder@latest --dump-assets=.workflow-builder-src # non-Imola-Kit-Pro projects: raw source, no patching

Development

npm install
npm run build      # tsc -> dist/
npm link           # test the `add-workflow-builder` command globally without publishing
node dist/index.js

Publishing

npm version patch                    # or minor / major
npm publish --access public          # npm will prompt for an OTP if the account has 2FA enabled

prepublishOnly runs npm run build automatically.

Keeping the bundled source in sync: assets/src/ and assets/locales/ are a snapshot copied from workflow-builder-component at the time this package was built — they do not update automatically if that project changes. Re-copy the relevant files and bump the version before publishing a new release.