Mateusz Burzyński

Bisects to https://github.com/microsoft/TypeScript/pull/57995 . It's unclear what you are asking for here. This is purely a display change, not a functional change.

If you could come up with repro steps - that would be immensely helpful in fixing this.

I think that it's likely that you had some other error before this happened, something failed to sync properly and impacted future sync - causing the duplicate layout strings to...

@viglucci @JoepKockelkorn could you try the newest version of the VS Code extension? Does the problem persist?

@JoepKockelkorn thank you for all of this detail! However, I fail to reproduce this with the given steps. The state is being added correctly - maybe it depends on where...

`moduleResolution: node` is removed and it's internally remapped to `moduleResolution: bundler` (I got this info from @jakebailey). This means that `package.json#exports` are always interpreted when they are present in `package.json`...

> Would you accept a PR to restore the serializability of the return value? I'd be interested in your take on the problem. When v2 was released I didn't realize...

I'm not sure what this issue is about. I think it might be about the signature help change because it has changed as follows: ```diff -my_func(inputs: Record): void +my_func(inputs: Record):...

> Given the PR mentioned by @Andarist (which I how no idea what it does or why it affects so many files) It's a diff between 2 nightly versions -...

I'd recommend using XState v4 and v5 side by side and migrating to v5 gradually. You want to make sure that the behavior of your system stays unaffected and that...