Runtime agnostic JS utils

# Using npm
npm i std-env

# Using pnpm
pnpm i std-env

# Using yarn
yarn add std-env

// ESM
import { env, isDevelopment, isProduction } from "std-env";

// CommonJS
const { env, isDevelopment, isProduction } = require("std-env");

• hasTTY
• hasWindow
• isDebug
• isDevelopment
• isLinux
• isMacOS
• isMinimal
• isProduction
• isTest
• isWindows
• platform
• isColorSupported
• nodeVersion
• nodeMajorVersion

You can read more about how each flag works from ./src/flags.ts.

std-env can automatically detect the current runtime provider based on environment variables.

You can use isCI and platform exports to detect it:

import { isCI, provider, providerInfo } from "std-env";

console.log({
  isCI, // true
  provider, // "github_actions"
  providerInfo, // { name: "github_actions", isCI: true }
});

List of well known providers can be found from ./src/providers.ts.

std-env can automatically detect the current JavaScript runtime based on global variables, following the WinterCG Runtime Keys proposal:

import { runtime, runtimeInfo } from "std-env";

// "" | "node" | "deno" | "bun" | "workerd" | "lagon" ...
console.log(runtime);

// { name: "node" }
console.log(runtimeInfo);

You can also use individual named exports for each runtime detection:

• isNetlify
• isEdgeLight
• isWorkerd
• isDeno
• isLagon
• isNode
• isBun
• isFastly

List of well known providers can be found from ./src/runtimes.ts.

std-env provides a lightweight proxy to access environment variables in a platform agnostic way.

import { env } from "std-env";

std-env provides a lightweight proxy to access process object in a platform agnostic way.

import { process } from "std-env";

MIT