Skip to main content
The current environment variables can be accessed via process.env.
https://mintcdn.com/bun-1dd33a4e-claude-docs-bunfig-missing-fields/ezY9cqHIbAlx71jp/icons/typescript.svg?fit=max&auto=format&n=ezY9cqHIbAlx71jp&q=85&s=fa9c9d5f512d0d81ae41ed65741d389aindex.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-claude-docs-bunfig-missing-fields/ezY9cqHIbAlx71jp/icons/typescript.svg?fit=max&auto=format&n=ezY9cqHIbAlx71jp&q=85&s=fa9c9d5f512d0d81ae41ed65741d389aindex.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.