Mateusz Burzyński
@andarist.bsky.social
programmer but also a little bit of code-poet wannabe, maintaining XState, Emotion, Changesets, redux-saga & more, OSS enthusiast
Have you missed the memo? I feel like people are doing this all the time - giving me anxiety 😬
November 7, 2025 at 5:03 PM
Have you missed the memo? I feel like people are doing this all the time - giving me anxiety 😬
If u’d make ur class nominal with private properties then it still wouldnt work but ur issue would become a duplicate of github.com/microsoft/Ty...
Don't suggest private fields in contexts where they are out of scope · Issue #56177 · microsoft/TypeScript
🔎 Search Terms private fields suggestions 🕗 Version & Regression Information This is the behavior in every version I tried, and I reviewed the FAQ for entries about private fields ⏯ Playground Link...
github.com
November 5, 2025 at 7:13 PM
If u’d make ur class nominal with private properties then it still wouldnt work but ur issue would become a duplicate of github.com/microsoft/Ty...
Its disputable what would be correct here - but i’d appreciate if all 3 of those would at least behave in the same way given they ultimately do exactly the same thing
July 6, 2025 at 8:05 PM
Its disputable what would be correct here - but i’d appreciate if all 3 of those would at least behave in the same way given they ultimately do exactly the same thing
Guilty as charged, that was my PR ;p
July 6, 2025 at 5:54 PM
Guilty as charged, that was my PR ;p
So u cant even do smth like
(params) => {
const { page } = params:
}
This wont match their regex ;p
(params) => {
const { page } = params:
}
This wont match their regex ;p
July 6, 2025 at 5:35 PM
So u cant even do smth like
(params) => {
const { page } = params:
}
This wont match their regex ;p
(params) => {
const { page } = params:
}
This wont match their regex ;p
Hm, im not sure if this applies to test functions but they parse fixture functions and literally look for the destructured argument in the source text of the function to learn what other fixtures are used by it - then, i imagine, they create the dependency tree (and init them in order) based on that
July 6, 2025 at 5:34 PM
Hm, im not sure if this applies to test functions but they parse fixture functions and literally look for the destructured argument in the source text of the function to learn what other fixtures are used by it - then, i imagine, they create the dependency tree (and init them in order) based on that
github.com
July 6, 2025 at 5:15 PM
Yes, emphasis is on all tests - we need to add extra instrumentation in tests and u cant do that from a reporter, we need to run code in the context of the test code. But we dont want to force users to import our instrumented fixture - they should continue using standard test import
July 6, 2025 at 5:13 PM
Yes, emphasis is on all tests - we need to add extra instrumentation in tests and u cant do that from a reporter, we need to run code in the context of the test code. But we dont want to force users to import our instrumented fixture - they should continue using standard test import
We found a hacky way to inject a custom fixture that runs for all tests so i can do some custom stuff before and after the use() call. Dont tell the Playwright team
July 6, 2025 at 4:47 PM
We found a hacky way to inject a custom fixture that runs for all tests so i can do some custom stuff before and after the use() call. Dont tell the Playwright team
It’s spooky… and boils down to the above inconsistencies with never - that generic has a base constraint of never
July 6, 2025 at 4:17 PM
It’s spooky… and boils down to the above inconsistencies with never - that generic has a base constraint of never
What truly prompted this was the situation from our codebase that i narrowed down to www.typescriptlang.org/play/?ts=5.9...
TS Playground - An online editor for exploring TypeScript and JavaScript
The Playground lets you write TypeScript or JavaScript online in a safe and sharable way.
www.typescriptlang.org
July 6, 2025 at 4:16 PM
What truly prompted this was the situation from our codebase that i narrowed down to www.typescriptlang.org/play/?ts=5.9...
That is correct! This is quite weird from the consistency’s standpoint 😢 i could even live with all of them not being errors, which could be a fair answer given `acceptString(accidentalNever)` is not an error and i dont imagine it being one
July 6, 2025 at 4:15 PM
That is correct! This is quite weird from the consistency’s standpoint 😢 i could even live with all of them not being errors, which could be a fair answer given `acceptString(accidentalNever)` is not an error and i dont imagine it being one
But i know where u are coming from :p
July 6, 2025 at 10:43 AM
But i know where u are coming from :p
To be clear - this particular PR introduces *situational* gains. The numbers are crazy for this one repo I was investigating (the one benchmarked there by Jake) - but in other codebases I've seen smaller gains (from 0% to 17% or smth, it just varies a lot and depends on ur code)
July 4, 2025 at 6:15 PM
To be clear - this particular PR introduces *situational* gains. The numbers are crazy for this one repo I was investigating (the one benchmarked there by Jake) - but in other codebases I've seen smaller gains (from 0% to 17% or smth, it just varies a lot and depends on ur code)
July 4, 2025 at 12:14 PM
To be clear - this particular PR introduces *situational* gains. The numbers are crazy for this one repo I was investigating (the one benchmarked there by Jake) - but in other codebases I've seen smaller gains (from 0% to 17% or smth, it just varies a lot and depends on ur code)
I feel like there are still great things to be achieved in TS feature-wise, most are probably just improvements and not some entirely new concepts. Perf is improtant too but the whole Go port is about that - and it also finds extra gains along the way (it's not just about porting to faster lang)
July 4, 2025 at 12:13 PM
I feel like there are still great things to be achieved in TS feature-wise, most are probably just improvements and not some entirely new concepts. Perf is improtant too but the whole Go port is about that - and it also finds extra gains along the way (it's not just about porting to faster lang)
I'm doing the same with my wife and it's a blast. We are reading out loud though so we are not moving as fast but we are still at like 14th or smth like that. We are currently at Hogfather and damn, this whole Death cycle is just a banger
July 3, 2025 at 7:11 AM
I'm doing the same with my wife and it's a blast. We are reading out loud though so we are not moving as fast but we are still at like 14th or smth like that. We are currently at Hogfather and damn, this whole Death cycle is just a banger
the fun part is those are kepts at those paths on disk, if u create foo branch and ur coworker creates foo/bar... well, u might end up with some annoying issues because of that
July 1, 2025 at 7:18 PM
the fun part is those are kepts at those paths on disk, if u create foo branch and ur coworker creates foo/bar... well, u might end up with some annoying issues because of that