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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@nan0web/release

v1.0.1

Published

Project Management as Code, Git-Native, GPG-Signed, Test-Driven

Readme

@nan0web/release

|Package name|Status|Documentation|Test coverage|Features|Npm version| |---|---|---|---|---|---| |@nan0web/release |🟢 97.1% |🧪 English 🏴󠁧󠁢󠁥󠁮󠁧󠁿Українською 🇺🇦 |🟡 84.2% |✅ d.ts 📜 system.md 🕹️ playground |— |

Project management as code, Git-native, GPG-signed, and test-driven.

Unlike traditional project tools that require constant syncing or manual updates, @nan0web/release enforces project structure where:

  • Tasks are represented as tests in .test.js files.
  • Status is tracked via test outcomes.
  • Team roles and approvals are stored in structured files.
  • All changes are signed, versioned, and composable.

This ensures:

  • Clear, automatable project tracking.
  • Immutable release notes and retro reflections.
  • Zero ambiguity – tasks don't exist unless tested.

Installation

How to install with pnpm?

pnpm add @nan0web/release

How to install with npm?

npm install @nan0web/release

How to install with yarn?

yarn add @nan0web/release

CLI Usage

Start by initializing a new release:

How to initialize a new release version?

release init v1.0.0

const cli = new ReleaseCLI() Show release details:

How to show release information?

release show [--full]

const release = new Release({ version: "v1.0.0", createdAt: new Date("2025-08-20") }) console.info(release.version) // v1.0.0 List all releases in the project:

How to list all releases?

release list [--json]

const cli = new ReleaseCLI() Add a chat message to the current release:

How to write a release chat message?

release chat write --user alice "Issue with the build pipeline"

const cli = new ReleaseCLI() Host a static server for viewing releases:

How to host release UI?

release host [--webui] [--port 3000]

const cli = new ReleaseCLI() Serve all release files for local inspection:

How to serve release static assets?

release serve [--port 8080]

const cli = new ReleaseCLI() Validate release tasks and integrity:

How to validate release tasks?

release validate [--ignore-fail]

const release = new Release({ version: "v1.0.0", createdAt: new Date("2025-08-20") }) Seal the release with retro reflection:

How to seal a release?

release seal [--message "All core APIs are stable and tested"]

const cli = new ReleaseCLI()

Core Concepts

1. Release as Object

A Release is a structured class containing:

  • version: release identifier (vX.Y.Z).
  • createdAt, startAt, planAt, completeAt: datetime milestones.
  • document: parsed markdown document with structure-aware parsing.

Each property is typed and validated automatically via JSDoc and runtime parsing.

How to instantiate a Release?

import { Release } from '@nan0web/release'
const release = new Release({
	version: "v1.0.0",
	createdAt: "2025-08-20T10:00:00Z"
})
console.info(release.version) // ← v1.0.0
console.info(release.createdAt instanceof Date) // ← true

2. Release Document Parsing

A ReleaseDocument extends @nan0web/markdown with:

  • Structured parsing of markdown release notes
  • Extraction of sections and tasks
  • Team and role parsing from markdown frontmatter or code

How to parse release notes markdown into structured data?

import { ReleaseDocument } from '@nan0web/release'
const md = `# v1.0.0 - 2025-08-20

## Overview
Release milestone includes UI polish and core API stabilization.

### Tasks
### Done **Implement core UI design** [ui.core-design]
### InProgress **Fix responsive issues in mobile layout** [ui.mobile-fixes]`

const doc = ReleaseDocument.from(md)
console.info(doc.version) // ← v1.0.0
console.info(doc.date instanceof Date) // ← true
console.info(doc.document.children instanceof Array) // ← true

3. Person & Team Structures

A Person instance includes:

  • name: HumanName
  • gender: HumanGender
  • contacts: array of HumanContact

How to create a Person with typed properties?

import { Person } from '@nan0web/release'
const person = new Person({
	name: ["Alice", "Developer"],
	gender: "female",
	contacts: ["mailto:[email protected]"]
})
console.info(person.name.firstName) // ← Alice
console.info(person.contacts.length >= 0) // ← true

Architecture: Project Management as Code

This architecture treats tasks as tests, roles as classes, and progress as validated outcomes.

Task Management

Tasks are registered as taskIdtestFilePath in ProjectManagement. Their status is derived by running node:test suites.

How to register and validate tasks as tests?

import { ProjectManagement } from '@nan0web/release'
const pm = new ProjectManagement()
pm.registerTask("task-1", "./tests/task1.test.js")
pm.registerTask("task-2", "./tests/task2.test.js")

const mockResults = {
	passed: ["task-1"],
	failed: [],
	pending: ["task-2"]
}

pm.validateProjectState = async () => mockResults
const results = await pm.validateProjectState()

console.info(results.passed.includes("task-1")) // ← true
console.info(results.pending.includes("task-2")) // ← true

Release Processing

The ReleaseManager coordinates releases and validates readiness. It ensures:

  • All registered tests pass
  • Version is correctly incremented
  • Git tag is applied if all validations succeed

How to execute a release after validation?

import { ReleaseManager, ProjectManagement } from '@nan0web/release'
const pm = new ProjectManagement()
const rm = new ReleaseManager(pm)

rm.calculateVersion = () => "v1.0.1"
rm.publish = async () => true

const result = await rm.executeRelease("patch")
console.info(result.version) // ← v1.0.1
console.info(result.published) // ← true

Changelog Integration

Using ChangelogTaskManager, you can:

  • Extract task definitions from changelog entries
  • Generate corresponding test files
  • Automate task progression in CI

How to parse changelog and extract tasks?

import { ChangelogTaskManager } from '@nan0web/release'
const ctm = new ChangelogTaskManager()
const changelog = `# Changelog

## [1.0.0] - 2025-08-20
### Added
- Initial structure [core.init]
- Release notes support [docs.release-notes]`

const tasks = ctm.parseChangelog(changelog)
console.info(Array.isArray(tasks)) // ← true
console.info(tasks.length >= 0) // ← true

Java•Script Features

Uses JSDoc and .d.ts files for autocompletion

CLI Playground

Try the package in the terminal:

How to run playground demo?

git clone https://github.com/nan0web/release.git
cd release
pnpm install
pnpm run playground

Project Status

To verify the project is ready, run:

How to check project status before publishing?

npm test
npm run test:coverage
npm run test:status

Contributing

How to contribute? - check here

License

How to license ISC? - check here