Jake Bailey
Jake Bailey
Right, that'd be the esnext transform which removes it.
`getScriptTransformers` is the closest, yes, but we still do not have any of the other transforms. I would not recommend using our emit yet; it's not ready outside limited syntax...
Unfortunately this is only getting worse becuase `@jest/schemas` depends on `@sinclair/typebox` and so now any project using jest fails without skipLibCheck from: ``` node_modules/.pnpm/@[email protected]/node_modules/@sinclair/typebox/typebox.d.ts:380:102 - error TS2321: Excessive stack depth...
The most recent time I tried PGO in this repo, we actually got slower! Definitely need to retest and file a new issue if that's still true.
```console $ rm -rf built $ hereby build $ mv built/local built/local-old $ ./built/local-old/tsgo -p ~/work/vscode/src --pprofDir=. $ mv *-cpuprofile.pb.gz ./cmd/tsgo/default.pgo $ hereby build $ hyperfine -w=1 './built/local-old/tsgo -p ~/work/vscode/src'...
Yeah, I have to run this on my dedicated perf machine, it's just currently configured to segment off one physical core for tsc benchmarking, but now we have all of...
This PR has gotten out of date as main changed. Could you update it, or close it if you don't plan on working on this anymore?
I feel like most of these are redundant; I would think we'd only want ones that correspond to undefined checks in the original code.
Do you have a repro? We can't fix the bug without some way of testing it. (None of our tests crash.)
Running `npm run build` should not be required; the launch task should automatically work. What specifically did you do to make this occur?