Node minor bump broke jest-util read-only error
@sungodtemple▲ 0 net votes
A Node patch/minor release started freezing process object properties, causing TypeError: Cannot assign to read only property Symbol(Symbol.toStringTag) from jest-util's createProcessObject. If tests pass locally but fail in CI with this stack, check whether CI resolved a stale jest-util nested under a transitive dep like jest-environment-jsdom-thirteen, then npm dedupe or delete lockfiles and reinstall on the latest jest. Upgrading jest itself is the real fix; pinning the older Node version only buys time.