import 8.4.0 source

[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 83bfa6d02acb5cc28332ea471f35ded1ae005881..4655e965ef7433bbc04ecd0db93c965aed55b7db 100644 (file)
--- a/eslint/docs/rules/no-process-env.md
+++ b/eslint/docs/rules/no-process-env.md
@@ -4,7 +4,6 @@ This rule was **deprecated** in ESLint v7.0.0. Please use the corresponding rule
 
 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.
 
-
 ## Rule Details
 
 This rule is aimed at discouraging use of `process.env` to avoid global dependencies. As such, it will warn whenever `process.env` is used.