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

@kubekpanel/blueprint-sdk

v0.2.0

Published

Type contract for Kubek server-type blueprints

Readme

@kubekpanel/blueprint-sdk

TypeScript type contract for Kubek blueprints — declarative server-type definitions describing how to download, install, launch, stop, detect status and query a game server.

This package is types only: it has no runtime code. It feeds the manifest validator, your editor's IntelliSense and the versions.ts resolver you ship inside a blueprint.

npm i -D @kubekpanel/blueprint-sdk
import type {
  KubekBlueprintManifest,
  VersionResolver,
} from "@kubekpanel/blueprint-sdk";

See the blueprint starter template for a complete, working example.

Docker runtime

runtime.kind selects how the panel launches the server: "native" (a host process) or "docker" (a container). All docker configuration lives in the optional dockerProfile field.

  • docker-only blueprint: runtime: { kind: "docker" } plus a dockerProfile.
  • dual-capable blueprint: runtime: { kind: "native" } plus a dockerProfile. The panel chooses the runtime when the server is created (global serverRuntime setting: auto / native / docker) and freezes that choice per server. Without Docker the blueprint behaves exactly like a native one.

dockerProfile.env is the single place where container env vars are mapped; every value supports {{...}} substitutions. Available tokens are the blueprint variables ({{JAVA_VERSION}}, {{GAME_VERSION}}, {{XMX}}, …) plus the host-supplied {{SERVER_DIR}}, {{HOST_UID}}, {{HOST_GID}}. Defaults: mounts → {{SERVER_DIR}}:/data, install → [{ type: "dockerPull", image }], stdinOpen → true, stop → the blueprint's startup.stop.

const paper: KubekBlueprintManifest = {
  // ...manifestVersion, id, variables (incl. JAVA_VERSION/GAME_VERSION/XMX), versions, install, startup...
  runtime: { kind: "native" },
  dockerProfile: {
    image: "itzg/minecraft-server:java{{JAVA_VERSION}}",
    stdinOpen: true,
    stop: { type: "signal:SIGTERM" },
    env: {
      EULA: "TRUE",
      TYPE: "PAPER",
      VERSION: "{{GAME_VERSION}}",
      MAX_MEMORY: "{{XMX}}M",
      OVERRIDE_SERVER_PROPERTIES: "false",
      PUID: "{{HOST_UID}}",
      PGID: "{{HOST_GID}}",
    },
  },
};