upgrade to v7.0.0

[pve-eslint.git] / eslint / docs / rules / no-process-env.md

diff --git a/eslint/docs/rules/no-process-env.md b/eslint/docs/rules/no-process-env.md
index 9db800fa153747d1587a4a72b69de558bf8b11b3..83bfa6d02acb5cc28332ea471f35ded1ae005881 100644 (file)
--- a/eslint/docs/rules/no-process-env.md
+++ b/eslint/docs/rules/no-process-env.md
@@ -1,5 +1,7 @@
 # Disallow process.env (no-process-env)
 
+This rule was **deprecated** in ESLint v7.0.0. Please use the corresponding rule in [`eslint-plugin-node`](https://github.com/mysticatea/eslint-plugin-node).
+
 The `process.env` object in Node.js is used to store deployment/configuration parameters. Littering it through out a project could lead to maintenance issues as it's another kind of global dependency. As such, it could lead to merge conflicts in a multi-user setup and deployment issues in a multi-server setup. Instead, one of the best practices is to define all those parameters in a single configuration/settings file which could be accessed throughout the project.