Under the hood
Useful1 Signal1
More process-wide variables became fields on a passed-around state object; behaviour is unchanged.
What's wrong with this entry?
Anonymous. No account, no email.
What
The cached user bucket hash, the telemetry-initialised latch, the process exit hook and the fullscreen-strike reset stopped being file-level variables and became fields on a state object handed to the functions that use them. Behaviour is unchanged; the state is just no longer global.
Evidence
cachedUserBucket
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.235
Process-wide caches are now scoped per host
Both mention state
-
v2.1.235
Per-session state replaces process-wide globals, and the render root takes explicit dependencies
Both mention state
-
v2.1.235
More file-scope variables replaced by accessor-backed containers
Both mention state