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

@starci/nest-kit

v0.2.1

Published

The shared building blocks of a StarCi back end that no capability owns: defineConfigurableModule and defineCapabilityModule, the typed one-line module definitions (register, registerAsync, the options token, isGlobal for a capability) whose exports state

Readme

@starci/nest-kit

The building blocks of a StarCi back end that no capability owns: the module definition and the class of a flow failure.

Every module of a back end has a <x>.module-definition.ts (R295). Written with Nest's ConfigurableModuleBuilder it is either an inferred surface (a destructured export the lint on stated export types, R368, refuses) or a typed builder with a Host type and re-exports that two modules of the same shape make a clone (R21, HFS_DUPLICATE_CODE). This package states the types once, so the definition is one call.

// platform/clock/clock.module-definition.ts: the representative module of a capability
import { defineCapabilityModule } from "@starci/nest-kit"
import type { ClockOptions } from "./clock.options"

export const { ConfigurableModuleClass, OPTIONS_TYPE } = defineCapabilityModule<ClockOptions>()

// features/api/hours/hours.module-definition.ts: any other module
import { defineConfigurableModule } from "@starci/nest-kit"
import type { HoursOptions } from "./hours.options"

export const { ConfigurableModuleClass, MODULE_OPTIONS_TOKEN, OPTIONS_TYPE, ASYNC_OPTIONS_TYPE } = defineConfigurableModule<HoursOptions>()

| export | for | |---|---| | defineConfigurableModule<Options>() | a sub-module, feature, transport or cli group: register / registerAsync, never global | | defineCapabilityModule<Options>(settings?) | the representative module of a capability: the same plus the isGlobal extra (default false); settings.optionsInjectionToken names the options token |

starci app codemod module-definition rewrites an existing app's definitions to these calls and adds the dependency.

Tests

npm test typechecks, lints and runs the node:test specs under 100% line coverage.

The class of a flow failure

classifyFailure(cause, DomainError) names what a failure means for a flow (BE-RESILIENCE-2): transient (a dropped or refused connection, a timeout, a lock or serialisation conflict) is retried with backoff; input (an error of the app's DomainError family), config (a domain code naming a configuration or connection) and code (anything else) park the flow, since a retry cannot help until the cause is fixed. An error that carries a failureClass names its own. The job runner of platform/jobs, the lite pgmq consumer and the full event runner all call it, so the rule has one home and no app capability exports a copy.

import { classifyFailure } from "@starci/nest-kit"
import { DomainError } from "@modules/platform/errors"

const parked = classifyFailure(cause, DomainError) !== "transient"