Security News
The Push to Ban Ransom Payments Is Gaining Momentum
Ransomware costs victims an estimated $30 billion per year and has gotten so out of control that global support for banning payments is gaining momentum.
Package description
The depd package is a deprecation helper for Node.js. It allows developers to mark functions, properties, and other JavaScript features as deprecated and to issue warning messages when they are used. This can be useful for library authors who want to make changes or remove features without breaking existing code that depends on their libraries.
Deprecate functions
This feature allows you to deprecate a function by wrapping it with a deprecation warning. When the function is called, it will log a deprecation message to the console.
var deprecate = require('depd')('my-module-name');
function oldFunction() {
deprecate('oldFunction is deprecated, use newFunction instead.');
// old function code
}
Deprecate property access
This feature allows you to deprecate access to an object property. When the property is accessed, it will log a deprecation message to the console.
var deprecate = require('depd')('my-module-name');
var obj = {};
Object.defineProperty(obj, 'oldProperty', {
get: function () {
deprecate('oldProperty is deprecated, use newProperty instead.');
return 'some value';
}
});
Customize deprecation messages
This feature allows you to customize the deprecation message for a property to provide additional information or instructions.
var deprecate = require('depd')('my-module-name');
deprecate.property(obj, 'oldProperty', 'oldProperty is deprecated and will be removed in the next major release.');
The deprecate package is similar to depd in that it allows you to mark functions as deprecated. However, it is more lightweight and does not provide the ability to deprecate properties or customize messages to the same extent as depd.
This package is a Node.js utility for marking deprecated APIs. It is similar to depd but is specifically designed to work with Node.js's built-in 'util' module. It provides a straightforward way to deprecate functions but does not support property deprecation.
Readme
Deprecate all the things
With great modules comes great responsibility; mark things deprecated!
$ npm install depd
var depd = require('depd')
var deprecate = depd('my-module')
This library allows you to display deprecation messages to your users. This library goes above and beyond with deprecation warnings by introspecting the call stack (but only the bits that it is interested in).
Instead of just warning on the first invocation of a deprecated function and never again, this module will warn on the first invocation of a deprecated function per unique call site, making it ideal to alert users of all deprecated uses across the code base, rather than just whatever happens to execute first.
The deprecation warnings from this module also include the file and line information for the call into the module that the deprecated function was in.
Create a new deprecate function that uses the given namespace name in the messages and will display the call site prior to the stack entering the file this function was called from. It is highly suggested you use the name of your module as the namespace.
Call this function from deprecated code to display a deprecation message. This message will appear once per unique caller site. Caller site is the first call site in the stack in a different file from the caller of this function.
If the message is omitted, a message is generated for you based on the site
of the deprecate()
call and will display the name of the function called,
similar to the name displayed in a stack trace.
Call this function to wrap a given function in a deprecation message on any call to the function. An optional message can be supplied to provide a custom message.
Call this function to wrap a given property on object in a deprecation message on any accessing or setting of the property. An optional message can be supplied to provide a custom message.
The method must be called on the object where the property belongs (not inherited from the prototype).
If the property is a data descriptor, it will be converted to an accessor descriptor in order to display the deprecation message.
This module will allow easy capturing of deprecation errors by emitting the
errors as the type "deprecation" on the global process
. If there are no
listeners for this type, the errors are written to STDERR as normal, but if
there are any listeners, nothing will be written to STDERR and instead only
emitted. From there, you can write the errors in a different format or to a
logging source.
The error represents the deprecation and is emitted only once with the same rules as writing to STDERR. The error has the following properties:
message
- This is the message given by the libraryname
- This is always 'DeprecationError'
namespace
- This is the namespace the deprecation came fromstack
- This is the stack of the call to the deprecated thingExample error.stack
output:
DeprecationError: my-cool-module deprecated oldfunction
at Object.<anonymous> ([eval]-wrapper:6:22)
at Module._compile (module.js:456:26)
at evalScript (node.js:532:25)
at startup (node.js:80:7)
at node.js:902:3
As a user of modules that are deprecated, the environment variable NO_DEPRECATION
is provided as a quick solution to silencing deprecation warnings from being
output. The format of this is similar to that of DEBUG
:
$ NO_DEPRECATION=my-module,othermod node app.js
This will suppress deprecations from being output for "my-module" and "othermod".
The value is a list of comma-separated namespaces. To suppress every warning
across all namespaces, use the value *
for a namespace.
NOTE This will not suppress the deperecations given to any "deprecation" event listeners, just the output to STDERR.
When a user calls a function in your library that you mark deprecated, they
will see the following written to STDERR (in the given colors, similar colors
and layout to the debug
module):
bright cyan bright yellow
| | grey cyan
| | | |
▼ ▼ ▼ ▼
my-cool-module deprecated oldfunction [eval]-wrapper:6:22
▲ ▲ ▲ ▲
| | | |
namespace | | location of mycoolmod.oldfunction() call
| deprecation message
the word "deprecated"
If the user redirects their STDERR to a file or somewhere that does not support
colors, they see (similar layout to the debug
module):
Sun, 15 Jun 2014 05:21:37 GMT my-cool-module deprecated oldfunction at [eval]-wrapper:6:22
▲ ▲ ▲ ▲ ▲
| | | | |
timestamp of message namespace | | location of mycoolmod.oldfunction() call
| deprecation message
the word "deprecated"
This will display a deprecated message about "oldfunction" being deprecated from "my-module" on STDERR.
var deprecate = require('depd')('my-cool-module')
// message automatically derived from function name
// Object.oldfunction
exports.oldfunction = deprecate.function(function oldfunction() {
// all calls to function are deprecated
})
// specific message
exports.oldfunction = deprecate.function(function () {
// all calls to function are deprecated
}, 'oldfunction')
This will display a deprecated message about "weirdfunction" being deprecated from "my-module" on STDERR when called with less than 2 arguments.
var deprecate = require('depd')('my-cool-module')
exports.weirdfunction = function () {
if (arguments.length < 2) {
// calls with 0 or 1 args are deprecated
deprecate('weirdfunction args < 2')
}
}
When calling deprecate
as a function, the warning is counted per call site
within your own module, so you can display different deprecations depending
on different situations and the users will still get all the warnings:
var deprecate = require('depd')('my-cool-module')
exports.weirdfunction = function () {
if (arguments.length < 2) {
// calls with 0 or 1 args are deprecated
deprecate('weirdfunction args < 2')
} else if (typeof arguments[0] !== 'string') {
// calls with non-string first argument are deprecated
deprecate('weirdfunction non-string first arg')
}
}
This will display a deprecated message about "oldprop" being deprecated from "my-module" on STDERR when accessed. A deprecation will be displayed when setting the value and when getting the value.
var deprecate = require('depd')('my-cool-module')
exports.oldprop = 'something'
// message automatically derives from property name
deprecate.property(exports, 'oldprop')
// explicit message
deprecate.property(exports, 'oldprop', 'oldprop >= 0.10')
The MIT License (MIT)
Copyright (c) 2014 Douglas Christopher Wilson
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
FAQs
Deprecate all the things
We found that depd demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Ransomware costs victims an estimated $30 billion per year and has gotten so out of control that global support for banning payments is gaining momentum.
Application Security
New SEC disclosure rules aim to enforce timely cyber incident reporting, but fear of job loss and inadequate resources lead to significant underreporting.
Security News
The Python Software Foundation has secured a 5-year sponsorship from Fastly that supports PSF's activities and events, most notably the security and reliability of the Python Package Index (PyPI).