Mateusz Burzyński
Mateusz Burzyński
I can see what could cause this but I somewhat fail to see *why* 🤔 This shouldn't increase the memory usage all that much: https://github.com/emotion-js/emotion/pull/3198/commits/89bebfbca7f75e441663072a3dcd9632a4ac3136 I can look into your...
Please report the issue where it should be fixed. The shape of this module is not incorrect so the bug is elsewhere. I see the issue with the types though,...
@tnortman-jabra it already exists (sort of): ```ts import { setup, fromCallback } from "xstate"; setup({ actors: { criticalCleanup: fromCallback(() => () => { // do stuff }), }, }).createMachine({ invoke:...
> We could allow root package name to be empty. It's not referred to from other namespaces and not published on npm, so the name is not used anywhere in...
It feels like a duplicate of https://github.com/microsoft/TypeScript/issues/58833
> ...that being said, if using spawnChild(), there's really nowhere else for the error to go. Could you show the exact situation you are talking about here?
I noticed it's fairly easy to lose those typeahead filters in watch mode (for example pressing Enter clears them). It's annoying but not a big deal. When debugging with VS...
@with-heart could u take a look at Knip's errors here?
The fork's permissions has changed and we no longer can push to it - that's the reason this work has been pulled into a fresh PR.
It would be good to know if https://github.com/microsoft/TypeScript/pull/60039 resolves this issue. Could any of you test it out using a build from that branch?