noProcessEnv

此内容尚不支持你的语言。

JavaScript (and super languages)

Summary

Rule available since: v1.9.1
Diagnostic Category: lint/style/noProcessEnv
This rule doesn’t have a fix.
The default severity of this rule is information.
Sources:
- Same as n/no-process-env

Description

Disallow the use of process.env.

The process.env object in Node.js stores configuration settings. Using it directly throughout a project can cause problems:

It’s harder to maintain
It can lead to conflicts in team development
It complicates deployment across multiple servers

A better practice is to keep all settings in one configuration file and reference it throughout the project.

Examples

Invalid

1
if (process.env.NODE_ENV === 'development') {
2
  // ...
3
}

code-block.js:1:5 lint/style/noProcessEnv ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ Don’t use process.env.
  
  > 1 │ if (process.env.NODE_ENV === ‘development’) {
      │     ^^^^^^^^^^^
    2 │   // …
    3 │ }
  
  ℹ Use a centralized configuration file instead for better maintainability and deployment consistency.

Valid

1
const config = require('./config');
2
if (config.NODE_ENV === 'development') {
3
  // ...
4
}

How to configure

1
{
2
  "linter": {
3
    "rules": {
4
      "style": {
5
        "noProcessEnv": "error"
6
      }
7
    }
8
  }
9
}