depd is a Node.js/JavaScript helper for marking APIs as deprecated and notifying users by displaying deprecation messages. It warns once per unique call site, includes namespace and file/line call location, and can emit deprecation errors via `process.on('deprecation', fn)` or suppress output with `NO_DEPRECATION` and `TRACE_DEPRECATION`.
Project status
- The source (dougwilson/nodejs-depd) does not show recent, frequent updates, with the latest tagged code updates listed in the provided history dating to v2.0.0 on 2018-10-26, and the last upstream push recorded as 2024-09-03, so it appears quiet or in maintenance mode rather than actively maintained as of today (2026-06-09).
- Apparent update cadence is very low, based on the absence of tagged updates after 2018 in the provided list, with only a later upstream push timestamp in 2024 and no additional details of intervening updates.
AI summary generated
Recent updates
v2.0.0
depd v2.0.0 modernizes the deprecation wrapper internals by removing older compat helpers and changing how deprecation stack sites and listener presence are computed. It also replaces the previous internal eval-based function wrapping with a Function-constructor based approach, while updating CI and tooling for newer Node.js versions.
Breakingv1.1.2
Release v1.1.2 focuses on a small performance/refactor change by removing argument reassignment patterns, plus expanding Node.js compatibility coverage up to 9.x. The only runtime code changes are internal variable handling in the deprecation logger logic, with no visible API or export surface changes.
v1.1.1
Release 1.1.1 updates depd to support a wider range of Node.js versions (claimed: 0.6 through 8.x) and removes an unnecessary dependency on the core Buffer module. The release notes only mention Buffer loading cleanup and Node version support, but the diff also removes an internal compat export used in tests.
v1.1.0
Release v1.1.0 expands depd to support io.js and newer Node.js versions, and adds a browser-specific entry point. It also enables 'use strict' in additional modules and introduces compatibility helpers for event listener counting.
Featuresv1.0.1
Release v1.0.1 primarily fixes how Depd generates auto messages and call site information, especially under 'use strict' where the previous implementation could throw TypeErrors. It also updates CI/test setup to include newer Node versions (Node 0.12 and io.js 1.x era) and modernizes badges and test tooling.
v1.0.0
This release (v1.0.0) has release notes stating there are no changes. The actual diff shows no source code modifications, but it does include a package version bump and documentation updates (README, History).
v0.4.5
Release 0.4.5 focuses on faster deprecation call handling and adding compatibility for Node.js 0.6. The code introduces a small compatibility layer for older Node runtimes, and updates stack trace formatting to use a call-site string formatter. It also updates test infrastructure and CI to cover the older Node version.
Featuresv0.4.4
Release v0.4.4 is described as a workaround for V8 generating empty stack traces. The diff shows a targeted change to stack capture logic in index.js to adjust how the stack is collected and sliced.
v0.4.3
Release v0.4.3 updates stack trace handling to prevent failures when the global Error.stackTraceLimit is set very low. It also adjusts tests to ensure call site logging still works under a low stack trace limit.
v0.4.2
Version 0.4.2 is a small change release focused on fixing the warning call site output. The release notes state that wrapped functions and properties now report the correct caller location.