Jake Bailey
Jake Bailey
Please see https://github.com/microsoft/TypeScript/pull/51806 / https://github.com/microsoft/TypeScript/issues/51789; this change cannot be made in tslib first.
I'll run tests on this but I highly suspect this will be super bad for breaks and perf @typescript-bot test it
@typescript-bot test it @typescript-bot pack this
Looking at the playground, I believe this does fix #58368, yes. - Before: [Playground Link](https://www.typescriptlang.org/play/?filetype=js#code/PQKhCgAIUgBBLAtgBwPYCcAukDeA5VAEwFMBnAX0gDN1VFIByRQgQ1MwahgRQ2xwAKqeADtMAGkhDS8TPFQjKNOowCuI+O07Rg4cKAjRIAcWLZMAC2KRUVKqTM2qkFpGQt0DwpHWbsaUUwAOi4uOHd0FnpBYTFKALEwyEgAFSsfDXY3WOxbSAB3C3gAYwtITFRIAHNHS2tbezMQo1h0M1V0EVJcEVVEACNidHIk1PSGh1znOoy-bMDmkF1iAA80LGp1YrkFarMhQIB5O0mACgTMAEpcKEg2zA6RSAM4TABPZGscXoGhyiXIOcckEJmZLuARvowGFTOZ0uwPFNGlMXG4PF5ZlkLoswrAIlFcAQSBRICIiMRRmlrL4sTknAUiqVypUanDrAiNqDgrj7o9ut8+oNhpT4ZhEU5kfSZjT-MCuMs1nxNiJtvInqyicQAMpirDHZGnMkka44W68zp7TAHMT6s4vWDvT64aSyNX-YCAo3EIJoGQ7ESXIIcq4QvQGGG1dLEETeLn01wRDEy+ZiHEtfHRTUkr0i6mZWWBemFEplCqW8pRmMSyaLODmro9QV-XOQaOxk6OPLS-Mp7k6cCrdbYKhbf2WzUAURjtrMhvJJrN7QtrOtmBnmFO9sdXxd-vdnvJPtQfrVgbb4JGQA) - After: [Playground Link](https://www.typescriptlang.org/play/?ts=5.8.0-pr-60921-3&filetype=js#code/PQKhCgAIUgBBLAtgBwPYCcAukDeA5VAEwFMBnAX0gDN1VFIByRQgQ1MwahgRQ2xwAKqeADtMAGkhDS8TPFQjKNOowCuI+O07Rg4cKAjRIAcWLZMAC2KRUVKqTM2qkFpGQt0DwpHWbsaUUwAOi4uOHd0FnpBYTFKALEwyEgAFSsfDXY3WOxbSAB3C3gAYwtITFRIAHNHS2tbezMQo1h0M1V0EVJcEVVEACNidHIk1PSGh1znOoy-bMDmkF1iAA80LGp1YrkFarMhQIB5O0mACgTMAEpcKEg2zA6RSAM4TABPZGscXoGhyiXIOcckEJmZLuARvowGFTOZ0uwPFNGlMXG4PF5ZlkLoswrAIlFcAQSBRICIiMRRmlrL4sTknAUiqVypUanDrAiNqDgrj7o9ut8+oNhpT4ZhEU5kfSZjT-MCuMs1nxNiJtvInqyicQAMpirDHZGnMkka44W68zp7TAHMT6s4vWDvT64aSyNX-YCAo3EIJoGQ7ESXIIcq4QvQGGG1dLEETeLn01wRDEy+ZiHEtfHRTUkr0i6mZWWBemFEplCqW8pRmMSyaLODmro9QV-XOQaOxk6OPLS-Mp7k6cCrdbYKhbf2WzUAURjtrMhvJJrN7QtrOtmBnmFO9sdXxd-vdnvJPtQfrVgbb4JGQA)
You can do: ``` every-ts bisect skip 9ff9c41a9a89dfeb8aed789c77aef8f329f5c0c1 ```
If so, that would be a major bug in VS Code or the LSP client library affecting practically any other request. The LS can't know about the first thing at...
The raw LSP logs would provide insight to that.
That is what me mean, the output window labeled LSP. Note that this contains loads of info including file contents.
The logs would be super helpful. You can send them to `jabaile at microsoft.com`.
So, it seems like everything is actually working correctly? (Where correctly means "`node10` resolution is unsupported, use `bundler`"?)