Mateusz Burzyński
Mateusz Burzyński
Please always try to share a repro case in a runnable form - either by providing a git repository to clone or a codesandbox. OSS maintainers usually can't afford the...
I'd like to review the upstream issue first - before landing this - because I think this should not be necessary and I want to know what's happening. I'll try...
The resolution I'd like to take here is to migrate our build setup to https://github.com/preconstruct/preconstruct/ . I have part of the work done on some old branch but never got...
We publish TS types to npm and they are available from the IDE. Not sure why WebStorm doesn't pick them up but I'm afraid that you would have to research...
I'm working on the improvements to the codeStudio syncing so hopefully that should resolve it. I'm not aware of any formatting loop though - more info about this would be...
An omitted expression like this is replaced with `any` so the overload selection mechanism essentially checks if the provided argument with type `{ type: any }` is assignable to the...
It's worth noting here that nowadays `package.json#exports` are a perfect replacement for the `process.env.NODE_ENV !== 'production'` convention (at the expense of complicating the build process)
Oh, I didn't realize that the website would load a file from the package with a dynamic import without processing this anyhow. I see 2 options here: - prepare a...
Hah, this is very interesting! I've created a playground with some additional checks ([here](https://www.typescriptlang.org/play?target=99&ts=4.8.4#code/C4TwDgpgBA4hDOwCuAnCBpCIoF4oCIATFAQwHN8oAfAsASwDsBjAC3wG4AoT0SKAYQD2AW2GCGAZWAlg0PAG8oYgG4RhEBsABcUANoMkwgEYQUAGigHjpgLpQAvl17QAIqTJSZcgSLGTpslAAZFCKhHSIJMwQOvqGJuaW8bYOTuDQAAqMrJ6BeEKi4rnQIYpRZAA2MUnWKKncjLIoAGYkTNDFoZxQUMTkAPw6buTFXD30zCyDUFmTo5z23M5QAKKqmgAq6fC4XT19ZDoZgo2maxrA1FAbgkis55pXALK38BAPlzSYIEaCJCiED5jKAAdxYEAgFR0AHVwZCgd0oPAmChBBUoVAAKoASQRPRU1WOpxQeKgLEEqhQRxOmjO62AwImrGpxI+VxudxYbJosIhFQRjiW6SgEhY-wghDgiFQEE6CkRBzIjDI01+aIgUS4gp4woAYkh0VLkGhigAeb5QCAAD1kDEIOyNMu+AD5dqLxZKEMbZQESoiAHLif0GiokIxVU3FXTfGzOrg6vgACSihCqKHNWEtNo09tgXqdWFdeAAFIjIrIdAB5YR0YCm-WG-Mm30ZkDOiz4CD0-DOzgASlwrqi2BoyhOhHjTHEiFBghQAGsdiXy9Vq7X6yHHc2vKaiO4ex2uxcewOcK75Iipwx4OqAHQVQRkYsr28E9SaPtayfTy6EQQITRoTnecdGTO0013A4e12Z9fVPc8y19REAHpkKgAA9fpuB6VCoGAFgIiRCFhB2YBBCgEwoBIKAmANMAUFrKi7SgRi-wAgByS43jUPDyMoqcUDQJhgERZZim+JcoHnLBBGaPD0lkpEkJwtCekwy9pzvB8nxfN8Lk-BZ42WDYvQARjdMU0E9aVt0CEICj8TpSl6CJpGiWIrASCxPNsdh6gTaATMQUyXmUXYguAUzdHwPTNHwGxOFwtSsIC64vQAJl2Nc6wi0zD27XtUoi9LQvCjLoti4B4q4JKMJS4yvQAZiyms63dKytx9Lxgh8Qp-G65zwkidy9B8xIxpsPz7Asdij00di4yFPgIsa0q8BWiqKTUY9JsS1S6qAA)) and I'm 100% certain that this is a bug in TypeScript. I've reported it [here](https://github.com/microsoft/TypeScript/issues/51331). So...
Vitest is using some weird strategy of bundling/resolving some things on its own but yet leaving some other things for node to resolve. I didn't dig deep enough to know...