depd依赖模块 - 编程技术参考——模具行业从业者必备知识手册

system 2

[![NPM Version][npm-version-image]][npm-url]
[![NPM Downloads][npm-downloads-image]][npm-url]
[![Node.js Version][node-image]][node-url]
[![Linux Build][travis-image]][travis-url]
[![Windows Build][appveyor-image]][appveyor-url]
[![Coverage Status][coveralls-image]][coveralls-url]

Deprecate all the things

<blockquote>
With great modules comes great responsibility; mark things deprecated!
</blockquote>

<h3>Install</h3>

This module is installed directly using <code>npm</code>:

<pre><code>
$ npm install depd
</code></pre>

This module can also be bundled with systems like
<a href="http://browserify.org/">Browserify</a> or <a href="https://webpack.github.io/">webpack</a>,
though by default this module will alter it's API to no longer display or
track deprecations.

<pre><code>
var deprecate = require('depd')('my-module')
</code></pre>

This library allows you to display deprecation messages to your users.
This library goes above and beyond with deprecation warnings by
introspection of 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.

NOTE this library has a similar interface to the <code>debug</code> module, and
this module uses the calling file to get the boundary for the call stacks,
so you should always create a new <code>deprecate</code> object in each file and not
within some central file.

<h4>depd(namespace)</h4>

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.

<h4>deprecate(message)</h4>

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 <code>deprecate()</code> call and will display the name of the function called,
similar to the name displayed in a stack trace.

<h4>deprecate.function(fn, message)</h4>

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.

<h4>deprecate.property(obj, prop, message)</h4>

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.

<h4>process.on('deprecation', fn)</h4>

This module will allow easy capturing of deprecation errors by emitting the
errors as the type "deprecation" on the global <code>process</code>. 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

<hr>
这个参数你们一般设多少？评论区说说。