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

create-omniflow-plugin

v0.1.0

Published

Scaffold a new OmniFlow plugin — Java ingestor/action + optional Next.js micro UI

Readme

create-omniflow-plugin

Interactive CLI scaffolder for OmniFlow plugins.

Generates a ready-to-build Gradle project with a Java ingestor, optional Next.js micro UI, and all the wiring needed to upload the plugin as a JAR to a running OmniFlow backend.

Usage

Run directly with npx (no install needed):

npx create-omniflow-plugin

Or with pnpm/yarn:

pnpm dlx create-omniflow-plugin
yarn dlx create-omniflow-plugin

The CLI will ask a few questions and scaffold a new directory named after your plugin ID.

Prompts

| Prompt | Description | |---|---| | Plugin ID | Lowercase, hyphen-separated identifier (e.g. gradle-build-scan) | | Display name | Human-readable name shown in the OmniFlow UI | | Description | Short description of what the plugin ingests | | Author | Your name or organisation | | Java base package | Root Java package (e.g. io.github.acme.plugins.myingestor) | | Ingestor type key | Used in API paths — /api/ingest/{type} | | Include Next.js UI? | Whether to scaffold a micro frontend | | OmniFlow plugin-api version | Version of omniflow-plugin-api to depend on | | OmniFlow API base URL | Backend URL for local UI dev (e.g. http://localhost:8080) |

What gets generated

<plugin-id>/
├── build.gradle          # Gradle build — Java + optional node-gradle plugin
├── settings.gradle
├── gradlew / gradlew.bat # Wrapper stubs (run `gradle wrapper` for the real ones)
├── src/main/java/…/
│   ├── <Name>Plugin.java     # OmniflowPlugin implementation
│   └── <Name>Ingestor.java   # PluginIngestor implementation
└── ui/                   # Only when "Include Next.js UI?" = yes
    ├── package.json
    ├── tsconfig.json
    ├── next.config.ts
    ├── tailwind.config.ts
    ├── postcss.config.mjs
    ├── eslint.config.mjs
    ├── .env.local
    ├── app/
    │   ├── globals.css
    │   ├── layout.tsx
    │   └── page.tsx
    ├── components/
    │   └── ThemeSync.tsx
    └── lib/
        └── api.ts

Build

Prerequisites

  • Java 25+ and Gradle on your PATH
  • Node.js 22+ (only required if you included the UI — node-gradle will download it automatically during ./gradlew jar)

Build the JAR

cd <plugin-id>
gradle wrapper        # generate the real Gradle wrapper (one-time)
./gradlew jar

The fat JAR is written to build/libs/<plugin-id>-1.0.0.jar. It includes all runtime dependencies and, if you chose to include a UI, the compiled Next.js static export embedded as resources.

To skip the UI build during development:

./gradlew jar -PskipUi

Upload to OmniFlow

curl -X POST http://localhost:8080/api/plugins/upload \
  -b "JSESSIONID=<your-session>" \
  -F "file=@build/libs/<plugin-id>-1.0.0.jar"

Replace http://localhost:8080 and the session cookie with your actual backend URL and credentials.

Develop the UI locally

When you include a Next.js UI you can run it standalone against a live OmniFlow backend — no JAR build required:

cd <plugin-id>/ui
npm install
npm run dev        # starts on http://localhost:3000

The NEXT_PUBLIC_API_URL variable in .env.local controls which OmniFlow backend the UI talks to.


Contributing to create-omniflow-plugin

Prerequisites

  • Node.js 18+
  • npm / pnpm

Install dependencies

npm install

Build

npm run build

Compiled output lands in dist/.

Watch mode (rebuild on save)

npm run dev

Test locally

node dist/index.js

Or link it globally so create-omniflow-plugin works in any directory:

npm link
create-omniflow-plugin

Publish to npm

  1. Bump the version in package.json.
  2. Build:
    npm run build
  3. Publish:
    npm publish --access public

The files field in package.json ensures only dist/ is included in the published package.