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

@maxal_studio/kratosjs-cli

v3.0.2

Published

Command-line interface for scaffolding KratosJs apps and plugins

Readme

@maxal_studio/kratosjs-cli

Command-line interface for scaffolding KratosJs apps and plugins.

Scaffold an app

npx @maxal_studio/kratosjs-cli new

The wizard asks for a project name, a database driver (MySQL, PostgreSQL, SQLite, MariaDB, or MongoDB), and an HTTP framework (Express, Fastify, Hapi, or Koa), then generates a ready-to-run full-stack app:

cd my-app
cp .env.example .env   # set your database credentials
npm run dev

The generated app is full-stack out of the box:

  • The admin panel is served at /admin (panel.panelPath('/admin')).
  • A server-rendered front page (SSR Views) is served at / — see src/views/pages/Home.tsx and the shared src/views/Layout.tsx (title, description, keywords, and favicon defaults live there).
  • Plugins are auto-wired on the client via virtual:kratos-client — you never edit src/admin/main.tsx to add one.

Flags: --driver <driver>, --http <adapter>, --no-install, --local (use file: links to a local monorepo checkout).

Build for production with npm run build (compiles the server, the admin bundle, and the views bundle) and run with npm start.

Scaffold a plugin

# server + React client (the default)
npx @maxal_studio/kratosjs-cli plugin my-plugin

# server-only (no React UI)
npx @maxal_studio/kratosjs-cli plugin my-plugin --no-client

A plugin is a standalone npm package. By default it ships both halves:

  • Server (. export) — a Plugin class whose register(panel) can add entities, migrations, resources, admin pages, routes, hooks, and public SSR view routes.
  • Client (./client export) — a definePluginClient manifest that contributes React to the panel: custom fields / columns / widgets / blocks, UI slots, and SSR view pages. The scaffold includes a sample custom field and a sample slot component (rendered under a record's details).

@maxal_studio/kratosjs-react, react, and react-dom are added as devDependencies so the client builds immediately. The generated package.json declares "kratosjs": { "client": "kratosjs-plugin-my-plugin/client" }, so the app's virtual:kratos-client module auto-imports the manifest — installing the plugin is enough; no entry-file edits.

cd kratosjs-plugin-my-plugin
npm install
npm run build

See the plugin docs for the full authoring guide.

Documentation