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

@vertesia/create-plugin

v0.82.1

Published

CLI to create Vertesia plugins: UI plugins or tool servers

Readme

@vertesia/plugin

CLI tool to create Vertesia plugins:

  • UI Plugins
  • Tool Server Plugins.

Usage

# Using pnpm create (recommended)
pnpm create @vertesia/plugin my-project

# Using npm create
npm create @vertesia/plugin my-project

# Using pnpm dlx (runs without installing)
pnpm dlx @vertesia/plugin my-project

# Using npx
npx @vertesia/plugin my-project

# Or install globally
pnpm install -g @vertesia/plugin
create-tool-server my-project

Note: When using pnpm create or npm create, drop the create- prefix from the package name.

Features

  • 📦 Downloads template from GitHub - Always get the latest template
  • ⚙️ Template-driven configuration - Template defines its own prompts via template.config.json
  • 🎨 Interactive prompts - User-friendly CLI with validation
  • 🔄 Variable replacement - Automatically replaces {{VARIABLES}} in files
  • 🧹 Smart cleanup - Removes meta files after installation
  • 📚 Package manager agnostic - Works with npm, pnpm, or yarn

How It Works

  1. Downloads the template repository from GitHub using degit
  2. Reads template.config.json from the template to determine configuration
  3. Prompts the user for values (project name, description, etc.)
  4. Replaces variables in specified files (e.g., {{PROJECT_NAME}}my-project)
  5. Cleans up meta files (.git, template.config.json, etc.)
  6. Installs dependencies using the configured package manager

Configuration

All configuration is centralized in src/configuration.ts:

export const config = {
  templateRepo: 'vertesiahq/plugin-template',
  templateConfigFile: 'template.config.json',
  packageManager: 'pnpm',
  // ... more options
}

Key Configuration Options

  • templateRepo - GitHub repository for the template (format: owner/repo)
  • templateConfigFile - Name of the config file in the template
  • packageManager - Which package manager to use (npm, pnpm, or yarn)
  • useCache - Whether to cache downloaded templates

Template Structure

The template repository should include a template.config.json file:

{
  "version": "1.0",
  "prompts": [
    {
      "type": "text",
      "name": "PROJECT_NAME",
      "message": "Project name",
      "initial": "my-tool-server"
    },
    {
      "type": "text",
      "name": "DESCRIPTION",
      "message": "Project description",
      "initial": "A tool server for LLM integrations"
    }
  ],
  "files": [
    "package.json",
    "README.md",
    "src/server.ts"
  ],
  "removeAfterInstall": [
    ".git",
    "template.config.json"
  ]
}

Template Config Schema

  • prompts - Array of prompts using the prompts library format
  • files - List of files where variable replacement should occur
  • removeAfterInstall - Files/directories to remove after installation
  • conditionalRemove - Conditional file removal based on user answers

Development

# Install dependencies
pnpm install

# Build
pnpm build

# Test locally
pnpm test

# Watch mode
pnpm dev

Publishing

# Build and publish
npm publish

After publishing, users can create projects with:

pnpm create @vertesia/plugin my-project

Template Development

To develop a template:

  1. Create a GitHub repository with your template files
  2. Add a template.config.json file with prompts and configuration
  3. Use {{VARIABLES}} in files where you want replacements
  4. Update src/configuration.ts to point to your template repo
  5. Test with pnpm test or run the built CLI directly

Examples

Create a project with default settings

pnpm create @vertesia/plugin my-project

View help

pnpm dlx @vertesia/plugin --help

License

MIT