Jake Bailey

Pack this failed to produce a playground for this due to a failure over here: https://github.com/microsoft/TypeScript-Make-Monaco-Builds/actions/runs/3341170061/jobs/5532095999 > node_modules/@types/node/globals.d.ts(72,13): error TS2403: Subsequent variable declarations must have the same type. Variable 'AbortSignal'...

@typescript-bot pack this (I can't answer your questions but I can rerun the task.)

Not sure if you've already considered it, but this would be a great breaking change to include in something like #2508. I've personally worked around this by doing something like...

I think that this is the same bug, but one thing I've noticed is that if you set `--external:./node_modules/*` but are targeting the CJS format, you will end up with...

After viewing some of the cross-linked PRs, I realized that I had completely glossed over the fact that you can just specify each package name as "external" directly, rather than...

I merged master into this PR to give it a test on some codebases; I found this case to be one that is also not handled. ```ts // index.ts import...

This likely negatively affects the new PIL stubs (#5594); in the ones I wrote that ship with Pylance (https://github.com/microsoft/python-type-stubs/tree/main/PIL), I made the stub `py.typed` with `partial` to avoid warnings about...

> 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...

Thanks for working on this! I'm currently running this on the TS codebase (as in some benchmarks, even our downleveled code for `??` with explicit `undefined`/`null` checks is faster than...

Does the same type safety work for the array? My guess was not (especially if we are using push to keep the array compact)