no need to re-implement process.noDeprecation

Also, the unbounded memory warning isn't a deprecation warning.
isaacs · Mar 17, 2022 · c5707e3 · c5707e3
1 parent 23708c7
commit c5707e3
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 3 deletions.
diff --git a/index.js b/index.js
@@ -24,9 +24,11 @@ const deprecatedProperty = (field, instead) => {
     warn(code, `${field} property`, `cache.${instead}`, get)
   }
 }
-const shouldWarn = (code) => typeof process === 'object' &&
+
+const shouldWarn = code => typeof process === 'object' &&
   process &&
-  !(process.noDeprecation || warned.has(code))
+  !warned.has(code)
+
 const warn = (code, what, instead, fn) => {
   warned.add(code)
   process.emitWarning(`The ${what} is deprecated. Please use ${instead} instead.`, 'DeprecationWarning', code, fn)

diff --git a/test/deprecations.js b/test/deprecations.js
@@ -1,7 +1,6 @@
 const t = require('tap')
 const LRU = require('../')
 
-process.noDeprecation = false
 const warnings = []
 process.emitWarning = (...w) => warnings.push(w)