Skip to main content
The current environment variables can be accessed via process.env.
https://mintcdn.com/bun-1dd33a4e-ciro-ws-proxy/5VvA5_lSqM955zlx/icons/typescript.svg?fit=max&auto=format&n=5VvA5_lSqM955zlx&q=85&s=2b3096741a4a19a7060ecd17dee174a4index.ts
process.env.API_TOKEN; // => "secret"

Bun also exposes these variables via Bun.env, which is a simple alias of process.env.
https://mintcdn.com/bun-1dd33a4e-ciro-ws-proxy/5VvA5_lSqM955zlx/icons/typescript.svg?fit=max&auto=format&n=5VvA5_lSqM955zlx&q=85&s=2b3096741a4a19a7060ecd17dee174a4index.ts
Bun.env.API_TOKEN; // => "secret"

To print all currently-set environment variables to the command line, run bun --print process.env. This is useful for debugging.
terminal
bun --print process.env
BAZ=stuff
FOOBAR=aaaaaa
<lots more lines>

See Docs > Runtime > Environment variables for more information on using environment variables with Bun.