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

@takuma-ru/rlse

v0.0.4

Published

All-in-one release flow execution package.

Readme

@takuma-ru/rlse

All-in-one release flow execution package.

Getting Started

1. Install

npm install @takuma-ru/rlse

2. Add script to package.json

{
  "scripts": {
    "rlse": "rlse"
  }
}

3. Run

npm run rlse

Configure settings via Setting file

Create rlse.config.ts in the project root and export a release flow. In addition to ts, the following file formats are supported.

  • rlse.config.ts
  • rlse.config.js
    • rlse.config.mjs
    • rlse.config.cjs
  • rlse.config.json

Example

import { defineConfig, presets } from "@takuma-ru/rlse";

export default defineConfig(
  presets.npmRelease({
    resolvePackage: { name: "vanilla-ts" },
    calculateNextSemver: {
      version: ({ currentVersion, inc }) =>
        inc(currentVersion, "prerelease", "beta")!,
    },
    runCommand: "pnpm build",
  }),
);

The release preset is built from small public steps. Use primitives directly when you need full control over side effects.

import { defineConfig, steps } from "@takuma-ru/rlse";

export default defineConfig([
  steps.checkCleanWorkingTree(),
  steps.checkNpmToken(),
  steps.checkAuth(),
  steps.resolvePackage({ name: "vanilla-ts" }),
  steps.resolvePublishedVersion({
    packageName: ({ results }) =>
      results.findStep("resolvePackage").packageName,
  }),
  steps.calculateNextSemver({
    currentVersion: ({ results }) =>
      results.findStep("resolvePublishedVersion").currentVersion,
    level: "patch",
  }),
  steps.writePackageVersion({
    packageJsonPath: ({ results }) =>
      results.findStep("resolvePackage").packageJsonPath,
    version: ({ results }) =>
      results.findStep("calculateNextSemver").nextVersion,
  }),
  steps.checkNpmPackageVersionAvailable({
    packageName: ({ results }) =>
      results.findStep("resolvePackage").packageName,
    version: ({ results }) =>
      results.findStep("calculateNextSemver").nextVersion,
  }),
  steps.updateChangelog({
    version: ({ results }) =>
      results.findStep("calculateNextSemver").nextVersion,
    changes: ["Release package."],
  }),
  steps.runCommand("pnpm build"),
  steps.stageFiles({
    paths: ({ results }) => [
      results.findStep("resolvePackage").packageJsonPath,
    ],
  }),
  steps.commit({ message: "Release vanilla-ts" }),
  steps.tag({
    name: ({ results }) =>
      `v${results.findStep("calculateNextSemver").nextVersion}`,
  }),
  steps.publishNpmPackage({ packageName: "vanilla-ts" }),
  steps.verifyPublishedNpmPackage({
    packageName: ({ results }) =>
      results.findStep("resolvePackage").packageName,
    version: ({ results }) =>
      results.findStep("calculateNextSemver").nextVersion,
  }),
  steps.githubRelease({
    tag: ({ results }) =>
      `v${results.findStep("calculateNextSemver").nextVersion}`,
  }),
  steps.push({ branch: "main" }),
]);

The default npm preset checks whether the next npm version is unpublished, publishes, verifies the package on the npm registry, commits before publishing, and pushes after publishing. If publish succeeds but push fails, rerun after fixing git access or push the created commit manually.

Available steps

The following steps are exported from steps.

| Step | Description | Options | | ------------------------------------------------ | ----------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | | steps.checkAuth() | Fails when GitHub CLI authentication is unavailable. | None. | | steps.checkGitHubAuth() | Fails when GitHub CLI authentication is unavailable. | None. | | steps.checkNpmToken() | Fails when npm authentication is unavailable. | None. | | steps.resolvePackage({ name }) | Finds the target package.json by package name and stores package metadata in the flow context. | name: package name. | | steps.resolvePublishedVersion(options) | Reads the currently published npm version for a package. | packageName, fallbackVersion. | | steps.calculateNextSemver(options) | Calculates the next semver version. | currentVersion, packageJson, level, pre, version. | | steps.writePackageVersion(options) | Writes a version to a package.json. Rolls back the file if the flow fails before commit or publish. | packageJsonPath, version. | | steps.updateChangelog(options) | Adds a version entry to a changelog and rolls it back if a later step fails. | version, path, date, changes. | | steps.runCommand(command, options) | Runs a shell command from the current working directory. | Same options as the internal command helper. | | steps.checkCleanWorkingTree(options) | Fails when the git working tree has uncommitted changes. | allowUntracked. | | steps.configureGitUser(options) | Configures local git author settings for the repository. | name, email. | | steps.createReleaseBranch(options) | Creates and switches to a local release branch. | branch. | | steps.stageFiles(options) | Stages files with git add. | paths. | | steps.commit(options) | Commits staged files. | message, skipIfNoChanges. | | steps.tag(options) | Creates a git tag and deletes it if a later step fails. | name, message. | | steps.checkNpmPackageVersionAvailable(options) | Fails when the target npm package version already exists. | packageName, version. | | steps.publishNpmPackage(options) | Publishes a package with npm publish. | packageName, packageDir, dryRun. | | steps.verifyPublishedNpmPackage(options) | Verifies that the published npm package version is visible on the registry. | packageName, version. | | steps.githubRelease(options) | Creates a GitHub Release with gh release create and deletes it if a later step fails. | tag, title, notes, draft, prerelease. | | steps.push(options) | Pushes a branch to a remote. | branch, remote, setUpstream. |

Custom steps can be added with (context) => { ... }.

CLI arguments can be declared with Zod in config and used when building the flow.

import { defineConfig, presets, z } from "@takuma-ru/rlse";

export default defineConfig({
  args: z.object({
    level: z
      .enum(["patch", "minor", "major", "preup"])
      .default("patch")
      .describe("Release level"),
    pre: z.boolean().default(false).describe("Release as pre-release"),
  }),
  flow: ({ args }) =>
    presets.npmRelease({
      resolvePackage: { name: "vanilla-ts" },
      calculateNextSemver: {
        level: args.level,
        pre: args.pre,
      },
      runCommand: "pnpm build",
    }),
});
rlse --level minor --pre

Use --dry-run to execute the flow without applying mutations such as writing versions, staging files, committing, tagging, configuring git, or pushing.

Multi-package releases

Rlse does not currently provide a coordinated multi-package release planner like Changesets or Lerna. For now, define one explicit flow per package, or compose multiple package flows manually when ordering and dependency bumps are simple. Use Changesets when you need change files, dependency graph updates, or a single release PR that coordinates many packages.

Comparison

Rlse focuses on explicit TypeScript release flows made from small steps.

| Tool | Best fit | Difference from Rlse | | ------------------ | --------------------------------------------------- | ------------------------------------------------------------------------------------------------------ | | semantic-release | Fully automated CI releases from commit history. | Rlse does not require Conventional Commits and keeps release logic explicit in code. | | release-it | Mature interactive or configured release workflows. | Rlse exposes smaller typed primitives and rollback-aware steps instead of a broad plugin-driven CLI. | | changesets | Coordinated monorepo package versioning. | Rlse does not manage changeset files or dependency graph bumps; use it for explicit per-package flows. | | lerna | Monorepo versioning and publishing. | Rlse is a release workflow runner, not a monorepo package manager. |

defineConfig Types

type RlseConfig<TArgs extends z.AnyZodObject = z.AnyZodObject> =
  | RlseFlowStep[]
  | {
      args: TArgs;
      flow: (context: { args: z.infer<TArgs> }) => RlseFlowStep[];
    };

type RlseFlowStep =
  | {
      name: string;
      run: (context: RlseContext) => unknown;
      rollback?: (
        context: RlseContext,
        result: RlseStepResult,
      ) => Promise<void> | void;
    }
  | ((context: RlseContext) => unknown);

License

Mozilla Public License Version 2.0