Frozen Config At Import Time Debugging Lab

Frozen Config At Import TimeConfig & EnvironmentMediumPreparing workspaceAutosaved

00:00

Incident Dossier

Frozen Config At Import Time

A small CLI reads its environment once at module load and freezes the result for the rest of the process. Test suites that swap `process.env` after importing the module see the old values, and a `DEBUG=1` toggled between tests has no effect on the running config.

Initial failing signalconfig reads process.env after the importExpected getConfig({ DEBUG: '1' }).debug === true · received getConfig({ DEBUG: '1' }).debug === false

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Inspect the module and see how its exported values are constructed.
Notice that the snapshot is taken at import time, not at call time.
Confirm that the helper ignores the env object the caller hands in.
Make the smallest correction so each call reads the env it is given.

Focus Mode

Start

src/config.js

Likely area

src/config.js

Progressive hints

Hints reveal broad direction first, then narrow toward the suspect path without showing hidden tests or exact solution code.

TopicConfig & Environment

DifficultyMedium

Est. time15 min

Workspacecreating

Explorer

Preparing workspace files…

Evidence Map

Failing signal loaded from challenge API
Workspace files loaded from workspace API
Results rendered only after API run/submit

Autosaved

workspace

Outputread-onlyready$ workspace boot

Workspace booting...