process-warning is a small utility for generating consistent Node.js warning objects across a codebase and emitting them in a controlled way. It includes helpers like createWarning and createDeprecation, and it can ensure a warning is issued only once (unless configured otherwise).
Project status
- Actively maintained, with the upstream push on 2026-08-06 and the most recent tagged updates on 2026-07-30 (v5.1.0), indicating ongoing development rather than dormancy.
- Apparent update cadence is fairly recent and frequent for this project, with a new tagged update in late July 2026 and additional upstream activity in early August 2026.
AI summary generated
Recent updates
v5.1.0
v5.1.0 adds a new `spyWarning()` helper to introspect warning calls for testing, and changes warning invocation to return whether the warning was actually emitted. The release also includes CI workflow permission/concurrency adjustments and several dev dependency bumps.
BreakingFeaturesv5.0.0
v5.0.0 focuses on repository and developer workflow updates. It reduces Dependabot frequency, updates CI branch coverage and Node versions, and migrates the test suite from tap to Node's built-in test runner (node:test) with coverage via c8.
v4.0.1
v4.0.1 primarily updates development and CI tooling, including upgrading the fastify/workflows CI template, expanding the Node test matrix to include Node 22, and switching linting from StandardJS to NeoStandard (via ESLint). The actual runtime code changes visible in the diff are minimal, with a small change to use node: prefixes in tests.
v4.0.0
v4.0.0 mainly updates documentation and development tooling. The code diff shows changes to CI workflow configuration, README text, .gitignore, and several devDependencies, with no runtime/library code changes shown.
v3.0.0
v3.0.0 is described in the release notes only as a refactor, but the code changes substantially alter the public API surface. The module no longer provides a manager object with create/emit/emitted, and instead exposes factory functions that return callable warning instances with their own emission state.
Featuresv2.3.2
Release v2.3.2 (published 2023-12-02) only notes a revert of v2.3.1 via PR #93, with no further detail. The actual code changes are concentrated in index.js, where the warning emission tracking logic and the exported shape of the internal `emitted` state were significantly altered.
v2.3.1
v2.3.1 makes the warning emission tracking logic more robust by removing reliance on a shared/global unlimited flag and replacing magic numbers with explicit state constants. It also adds a regression test to ensure creating multiple warning codes does not cause the unlimited configuration to be overwritten across codes.
v2.3.0
v2.3.0 adds support for creating Node.js-style deprecation warnings via a new `createDeprecation` helper on the warning manager. The release also updates documentation and tests around warning suppression (`--no-warnings`, `NODE_NO_WARNINGS`, `NODE_OPTIONS`), and includes small CI and dependency maintenance changes.
Featuresv2.2.0
v2.2.0 adds an option to make warnings emit unlimited times. It also updates TypeScript type definitions and documentation for the new `warning.create(..., options)` signature, plus some repo tooling tweaks.
Featuresv2.1.0
v2.1.0 focuses on modernizing the development toolchain (test runner migration to tap, added license checking and linting in CI) and bumping several dev dependencies like jest and tsd. The implementation also includes a small performance-oriented change around emit() and updates TypeScript typings by moving them into a types/ folder.
Features