@gj-kit/nest-operations-jobs
NestJS composition for durable, authenticated, observable operational jobs with explicit store ports.
Current npm latest:
0.1.1
Use it when
Section titled “Use it when”Use it when a Nest application needs scheduled or operator-triggered work with explicit concurrency, authorization, and run persistence.
Do not use it when
Section titled “Do not use it when”Do not hide product business rules, queue infrastructure, or application authorization policy behind this integration.
Golden path
Section titled “Golden path”Outcome: An authenticated operations boundary backed by application-owned run storage.
1. Install
Section titled “1. Install”pnpm add @gj-kit/nest-operations-jobs2. Keep the app-owned boundary explicit
Section titled “2. Keep the app-owned boundary explicit”Implement JobRunStore, then configure a 32+ character shared secret or a token verifier before module registration.
3. Start with the smallest integration
Section titled “3. Start with the smallest integration”Copy this first, then replace only the app-owned values named above.
import { OperationsJobsModule, type JobRunStore } from '@gj-kit/nest-operations-jobs';
declare const store: JobRunStore; // Your database-backed run store.declare const secret: string; // At least 32 characters; keep it outside source control.
export const operations = OperationsJobsModule.forRoot({ store, auth: { secret }, trigger: { path: 'internal/jobs' },});Runtime and peers
Section titled “Runtime and peers”Engines: node >=20
| Peer | Supported range | Required for |
|---|---|---|
@nestjs/common |
`^10 | |
@nestjs/core |
`^10 | |
reflect-metadata |
`^0.1.13 | |
rxjs |
^7 |
the package integration |
Public subpaths
Section titled “Public subpaths”| Entry | Exported symbols |
|---|---|
Root entry |
60 |
./core |
61 |
./testing |
13 |
Safety boundary
Section titled “Safety boundary”Keep job-trigger authorization and app data ownership in the host application. Never turn a convenience route into an unauthenticated operations endpoint.
API reference
Section titled “API reference”complete API reference contains every public function, class, type, constant, and error contract generated from release declarations. Each item shows its import path, release signature, and package version.