noProcessGlobal

Ta treść nie jest jeszcze dostępna w Twoim języku.

JavaScript (and super languages)

Summary

Rule available since: v2.0.0
Diagnostic Category: lint/correctness/noProcessGlobal
This rule has a safe fix.
The default severity of this rule is information.
Sources:
- Same as deno-lint/no-process-global

How to configure

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

Description

Disallow the use of process global.

Node.js and Deno expose process global but they are hard to statically analyze by tools, so code should not assume they are available. Instead, import process from "node:process".

Examples

Invalid

1
const foo = process.env.FOO;

code-block.js:1:13 lint/correctness/noProcessGlobal  FIXABLE  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ Usage of the process global is discouraged.
  
  > 1 │ const foo = process.env.FOO;
      │             ^^^^^^^
    2 │ 
  
  ℹ process global is hard for tools to statically analyze, so code should not assume they are available.
  
  ℹ Safe fix: Add import process from &quot;node:process&quot;; to this file’s imports.
  
      1 │ + import·process·from·“node:process”;
    1 2 │   const foo = process.env.FOO;
    2 3 │

Valid

1
import process from "node:process";
2

3
const foo = process.env.FOO;

The rule is not able to detect cases where the global object is aliased:

1
const foo = globalThis;
2
const bar = foo.process;