Jake Bailey

I've noticed this storage problem too, but I also have found stack traces to be valuable in diagnosing previous crashes on DT. It'd be nice if corepack had some sort...

This doesn't feel too dissimilar to https://github.com/typescript-eslint/typescript-eslint/issues/1192#issuecomment-1905319863.

And if his happens at the CLI, running it via pprof-it would be pretty helpful.

I would think that the moment you're doing something unsafe like casting an enum or `ts-ignore`ing, all bets are off about actual runtime behavior. The only "safe" thing I think...

It shouldn't be related to #53955 since that one happens even when compiling with `tsc`, whereas this issue appears to only happen once you edit something.

> If Jedi is doing this, it should stop. This is a big security vulnerability, and someone with malicious intent will eventually exploit it. IIRC Jedi does for compiled code...

If you're targeting es5 in your webpack config, then this file should be getting downleveled in syntax by webpack or babel or similar; this file is `.mjs` after all and...

It'd be an issue in both; this library is just the same helpers that TS emits but pulled out for common reuse. @rbuckton

I tested this out on hereby as a low-risk test before we do this to critical packages, and unfortunately it didn't seem to work: https://github.com/jakebailey/hereby/actions/runs/5483129736/jobs/9989176122#step:11:404

With 1.8.0 out, I got my first working SLSA level 3 build: https://github.com/jakebailey/hereby/actions/runs/5768389689 Feel free to copy my (now working) pipeline for this, though we'll have to get it into...