@effect/tsgo

97d3c56: Track the typescript@beta dist-tag alongside typescript@latest and typescript@next. repoctl upstream update now resolves the beta tag into upstream.json, so the TypeScript beta compiler (currently 7.1.0-beta) is built, tested in CI under the beta channel, and shipped with the platform packages.

eb044ca: Update the TypeScript next tag to typescript@next, which ships typescript-go commit 28534d7609062699a68b1b66e2367f8d95dbf290, update the TypeScript beta tag to typescript@beta, and update the TypeScript latest tag to typescript@latest.

d53a707: Add the opt-in preferEffectString diagnostic in effectNative for native String method invocations. It suggests 32 effect/String counterparts, including trimLeft to String.trimStart and trimRight to String.trimEnd.

Each suggestion explains typing or runtime differences. For example, email.indexOf("@") suggests String.indexOf, which returns Option with None replacing -1.

The rule defaults to off and the effect-native preset enables it as a warning. Both Effect v3 and v4 are supported. Only suppression quick fixes are available.

70bb791: Update the TypeScript next tag to typescript@next, which ships typescript-go commit 5237fd46890956e4bb8177a1a05dcd69e4166560, and update the TypeScript latest tag to typescript@latest. Refresh the Oxlint configuration schema from the selected package.

e00f33c: Add the schemaClassObjectLiteral diagnostic. It warns when an object literal is checked as a Schema class instance. A plain object has no class prototype, so instanceof, class methods, and Schema encoding fail at runtime. A Schema brand does not help, because a spread copies the brand property.

class User extends Schema.Class<User, { readonly brand: unique symbol }>("User")({ name: Schema.String }) {}

const copy: User = { ...user } // warning: build it with User.make({ ...user })
const renamed = User.make({ ...user, name: "b" }) // ok

In Effect v4, the rule skips objects nested inside a Schema constructor call, such as Parent.make({ child: { ...child } }), because v4 builds the nested class instance from the plain object.

c83ee4d: runEffectInsideEffect now reports Effect.runSyncExit and Effect.runPromiseExit, the same as Effect.runSync and Effect.runPromise. The quick fix rewrites them to Effect.runSyncExitWith and Effect.runPromiseExitWith in Effect v4, and to Runtime.runSyncExit and Runtime.runPromiseExit in Effect v3.

export const nested = Effect.gen(function*() {
  yield* Effect.void
  setTimeout(() => {
    Effect.runPromiseExit(child)
    // ^- `Effect.runPromiseExit` is called inside an Effect with a separate services invocation.
  }, 0)
})

de42db0: Update the TypeScript next tag to typescript@next, which ships typescript-go commit 5237fd46890956e4bb8177a1a05dcd69e4166560, and update the TypeScript latest tag to typescript@latest.