Records/npm/dotenv/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• 17.4.2 PASS 1 passing observations
• 17.3.1 not measured
• 16.6.1 FAIL
• 16.4.5 PASS 1 passing observations

Where it reproduced

• executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×10 2026-08-29 → 2026-09-01

Nearest known PASS/FAIL boundaries

The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.

• Last passing release 16.4.5 → first failing release 16.6.1

  One side of this boundary has no resolved dependency tree, so nothing could be compared.

• Last failing release 16.6.1 → first passing release 17.4.2

  Releases between them never measured at this stage: 1

  One side of this boundary has no resolved dependency tree, so nothing could be compared.

Evidence gaps

• Releases in this window never measured at PROJECT_TEST: 1
• No resolved dependency tree for 16.4.5 or for 16.6.1, so the versions either side of the boundary could not be compared.
• No failure domain was inferred for this failure.

Published answers for the affected releases

• dotenv 16.6.1 Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWnode 22.23.2 MIT-0 · 2026-08-23
• dotenv 16.6.1: process.env is undefined in an ESM module even though dotenv.config() ran and .env exists Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. FIXdotenv.configdotenv/confignode 22 MIT-0 · 2026-08-13