update typescript to 5.4

[tim-smart]

No description provided.

[changeset-bot]

🦋 Changeset detected

Latest commit: 0e1decd

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 16 packages

Name	Type
@effect/schema	Patch
@effect/cli	Patch
effect	Patch
@effect/experimental	Patch
@effect/opentelemetry	Patch
@effect/platform	Patch
@effect/platform-browser	Patch
@effect/platform-bun	Patch
@effect/platform-node	Patch
@effect/platform-node-shared	Patch
@effect/printer	Patch
@effect/printer-ansi	Patch
@effect/rpc	Patch
@effect/rpc-http	Patch
@effect/typeclass	Patch
@effect/vitest	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[tim-smart]

@gcanti Looks like there is an issue with Schema.tuple

[gcanti]

@tim-smart wow... it seems that there has been a significant change in the behavior of the built-in type Required when it comes to tuples

from

// ts 5.3
type A = readonly [string, ...number[], boolean]
type B = Required<A> // readonly [string, ...(number | boolean)[], number | boolean]

to

// ts 5.4
type A = readonly [string, ...number[], boolean]
type B = Required<A> // readonly [string, ...number[], boolean]

[tim-smart]

The typescript 5.3 behaviour seems strange, unless I'm missing something.

[gcanti]

The 5.4 behaviour seems definitely more correct, probably a bugfix, all previous versions behaved differently, and I had to implement the "wrong" behaviour to keep runtime and type-level aligned. I think we should change the runtime to align with version 5.4

[tim-smart]

This will mean mis-alignment for previous typescript versions? I wonder if this should be in the next minor release.

[gcanti]

yes, but in any case, we have a mis-alignment, either with the previous versions or with version 5.4. However, the behaviour of version 5.4 is the "correct" one, so I would prioritize it and treat it as a bugfix