node/no-process-env Restriction

Disallows use of process.env.

Directly reading process.env can lead to implicit runtime configuration, make code harder to test, and bypass configuration validation.

Examples of incorrect code for this rule:

if (process.env.NODE_ENV === "development") {
  // ...
}

Examples of correct code for this rule:

import config from "./config";

if (config.env === "development") {
  //...
}

Configuration

This rule accepts a configuration object with the following properties:

type: string[]

default: []

Variable names which are allowed to be accessed on process.env.

To enable this rule using the config file or in the CLI, you can use:

Config (.oxlintrc.json)Config (oxlint.config.ts)CLI

json

{
  "plugins": ["node"],
  "rules": {
    "node/no-process-env": "error"
  }
}

import { defineConfig } from "oxlint";

export default defineConfig({
  plugins: ["node"],
  rules: {
    "node/no-process-env": "error",
  },
});

bash

oxlint --deny node/no-process-env --node-plugin

This rule was added in v1.23.0.