dotenv: expose auto-loaded .env values as non-enumerable on process.env - #35481
Closed
robobun wants to merge 14 commits into
Closed
dotenv: expose auto-loaded .env values as non-enumerable on process.env#35481robobun wants to merge 14 commits into
robobun wants to merge 14 commits into
Claude / Claude Code Review
completed
Jul 25, 2026 in 23m 33s
Code review found 1 potential issue
Found 1 candidates, confirmed 1. See review comments for details.
Details
| Severity | Count |
|---|---|
| 🔴 Important | 0 |
| 🟡 Nit | 1 |
| 🟣 Pre-existing | 0 |
| Severity | File:Line | Issue |
|---|---|---|
| 🟡 Nit | docs/runtime/environment-variables.mdx:144-146 |
Docs: 'bun --print process.env' example now omits auto-loaded .env values |
Annotations
Check warning on line 146 in docs/runtime/environment-variables.mdx
claude / Claude Code Review
Docs: 'bun --print process.env' example now omits auto-loaded .env values
The new **Enumeration** section correctly documents that auto-loaded `.env` values are non-enumerable, but line 163 of the same file still says "To print all currently-set environment variables, run `bun --print process.env`" — after this PR that command omits auto-loaded `.env` values (POSIX inspect shows only enumerable own properties; on Windows the new `enumerableView` filters by `.enumerable`), so users debugging "is my .env loading?" will see nothing from `.env`. `docs/guides/runtime/read-
Loading