@effect/language-service

Update Effect v4 support to 4.0.5 and fix runEffectInsideEffect.

Effect.runPromiseExit and Effect.runSyncExit called inside an Effect are now reported, like Effect.runPromise and Effect.runSync:

export const program = Effect.gen(function* () {
  yield* Effect.void;
  setTimeout(() => {
    Effect.runPromiseExit(child);
    // ^- now suggests Effect.runPromiseExitWith (v4) or Runtime.runPromiseExit (v3)
  }, 0);
});

The v4 quick fix now inserts yield* Effect.context<never>() instead of the removed Effect.services, and reuses an existing yield* Effect.context() binding:

export const program = Effect.gen(function* () {
  const context = yield* Effect.context<never>();
  const run = () => Effect.runSyncWith(context)(Effect.succeed(1));
  return [context, run()] as const;
});

missedPipeableOpportunity now reports calls whose result is used as a method receiver, and the calls nested inside them. These were skipped before:

// now reported: `Inner.pipe(...)`
export const B = Schema.NullishOr(Inner).annotations({ identifier: "B" });

// now reported, including the nested `Schema.Array(Inner)`
export const C = Schema.NullishOr(
  Schema.Struct({ x: Schema.Array(Inner) })
).annotations({ identifier: "C" });

Other diagnostics built on the same piping analysis, such as flatMapToMap and strictEffectProvide, now also check calls in these positions.

Update Effect v4 compatibility to 4.0.0-beta.107.

Update Effect v4 compatibility to 4.0.0-rc.115 and allow Effect.provide at recognized application entry points.

Update Effect v4 compatibility to 4.0.0-rc.118. Migrate CLI, HTTP, schema model, and encoding imports to the new package paths, including the v4 examples and diagnostics.

Update Effect v4 compatibility to 4.0.0-beta.104, including the renamed Schema.Error and Schema.TaggedError constructors.