I've spotted a new label in the TypeScript repo and I dig it 🤣
Mateusz Burzyński
13.6K posts
Mateusz Burzyński
@AndaristRake
programmer but also a little bit of code-poet wannabe, maintaining XState, Emotion, redux-saga & more, OSS enthusiast
- Oh, yeeeeah, this has been merged 😍😍😍😍😍😍😍😍😍 TS 5.5 is gonna be one of the most epic releases in a while, once again - huge props to @danvdk
- A code snippet like this saved me already *multiple times* when investigating why the focus shifts somewhere unexpectadly
- You all will love this, such a great DX improvement ❤️
- Just noticed my name in the TS 5.0 release notes, not bad for a junior dev
- OMG, you only tell me now about this?! { "jest": { "snapshotFormat": { "printBasicPrototype": false } } }
- This is not a drill! Improvements to the *in operator* might be coming in TS 4.9 🔥🔥🔥 github.com/microsoft/Type…
- I'm supposed to be good at TypeScript but typing generic wrappers around React.forwardRef is... 🫠
- One dev "super power" that I have is debugging... how do I teach this to others?
- I'll remember the world before and after this PR: github.com/microsoft/Type… The new era of conditional types checking is coming in TypeScript 5.8!
- Reverse mapped types are just so super elegant for certain use cases... Here we have an equivalent of `Promise.allSettled` that retains positional information for each item in the input typescriptlang.org/play?ts=5.3.2#…
![type SettledResult<T> =
| { status: "fulfilled"; value: T }
| { status: "rejected"; reason: unknown };
declare function promiseAllSettled<T extends readonly unknown[]>(
promises: [...{ [K in keyof T]: Promise<T[K]> }],
): {
[K in keyof T]: SettledResult<T[K]>;
};
const p1 = Promise.resolve("");
const p2 = Promise.resolve(10);
const result = promiseAllSettled([p1, p2]);
// ^? const result: [SettledResult<string>, SettledResult<number>]](https://pbs.twimg.com/media/GCxphb8XEAAb5tc.jpg)
- I'm reading v8 source code to understand how promises are created and chained internally... what my life has become
