@effect/language-service@0.87.1

Patch Changes

• #765 6b9dab5 Thanks @mattiamanzati! - Ignore Effect v4 local Effect.provide(..., { local: true }) calls when reporting chained provides with the multipleEffectProvide diagnostic.

@effect/language-service@0.87.0

Minor Changes

• #760 f1fca78 Thanks @mattiamanzati! - Add the flatMapToMap style diagnostic, which suggests replacing Effect.flatMap((value) => Effect.succeed(f(value))) with Effect.map((value) => f(value)).

Patch Changes

• #762 5e71871 Thanks @mattiamanzati! - Enable skipLibCheck in the diagnostics test harness to reduce test runtime and memory usage.

• #763 0dc8034 Thanks @mattiamanzati! - Update the setup command to configure VS Code with the unified js/ts TypeScript settings.

• #742 939a049 Thanks @RezaOwliaei! - Update README to replace deprecated VSCode TypeScript settings (typescript.tsdk and typescript.enablePromptUseWorkspaceTsdk) with the current recommended configuration.

@effect/language-service@0.86.6

Patch Changes

• #758 6ef9a46 Thanks @mattiamanzati! - Skip Effect diagnostics for external library files in patched tsc runs when TypeScript skipLibCheck is enabled.

@effect/language-service@0.86.5

Patch Changes

• #751 8d0b85a Thanks @mattiamanzati! - Reject unsupported TypeScript versions when loading or patching TypeScript, directing TypeScript 7 users to @effect/tsgo.

• #754 1dce66b Thanks @mattiamanzati! - Update the Effect v4 harness and language-service development dependencies to Effect 4.0.0-beta.94, including compatibility updates for the latest Effect API and Schema type output.

@effect/language-service@0.86.4

Patch Changes

• #746 5da9914 Thanks @mattiamanzati! - Avoid suggesting removal of Effect.gen when a single return statement contains multiple yield* expressions, which would produce invalid code.

@effect/language-service@0.86.3

Patch Changes

• #744 1707983 Thanks @mattiamanzati! - Fix lazyPromiseInEffectSync false positives for Effect.sync thunks whose return type degrades to any. Promise detection now ignores any and unknown before falling back to assignability against the global Promise type.

• #740 df50dfc Thanks @jbmusso! - Fix effectRpcDefinition wiping the upstream go-to-definition result when the user clicks on a JSX <Namespace.Component /> tag name. The plugin's RpcClient → Rpc enrichment now skips ancestor nodes whose type cannot be resolved (such as JSX tag-name nodes) instead of returning undefined for the entire request.

@effect/language-service@0.86.2

Patch Changes

• #739 2a21b07 Thanks @mattiamanzati! - Update the generated schema.json to include the TypeScript 6.0 ES2025 target and lib entries.

• #738 ec42fd6 Thanks @mattiamanzati! - Update preferSchemaOverJson to be off by default.

  Improve the diagnostic guidance for JSON parsing and stringifying:

  • in Effect v3, suggest Schema.parseJson(Schema.Unknown) for unknown shapes and Schema.parseJson(schema) for known ones
  • in Effect v4, suggest Schema.UnknownFromJsonString, Schema.fromJsonString(schema), and Schema.toCodecJson(schema) depending on whether the target shape is known and whether the code is working with JSON strings or JSON values

• #736 4bf81c4 Thanks @mattiamanzati! - Update the Effect v4 beta dependencies to 4.0.0-beta.68.

@effect/language-service@0.86.1

Patch Changes

• #732 0674371 Thanks @mattiamanzati! - Update the Effect v4 test harness and language service development dependencies to Effect 4.0.0 beta 66, including fixture updates for the latest Context service API.

@effect/language-service@0.86.0

Minor Changes

• #728 a5b0e47 Thanks @mattiamanzati! - Add the unsafeEffectTypeAssertion diagnostic to catch as Effect<...>, as Stream<...>, and as Layer<...> assertions that unsafely narrow the error or requirements channels.

  The rule skips channels whose original type is any and offers a quick fix that removes the assertion while preserving the original expression.

@effect/language-service@0.85.1

Patch Changes

• #726 fd4a8da Thanks @mattiamanzati! - Update the Effect v4 beta examples and type parsing to match the renamed Context APIs in the latest 4.0.0-beta releases.

• #724 14d5798 Thanks @mattiamanzati! - Refactor Effect context tracking to use cached node context flags and direct generator lookups.

  This aligns the TypeScript implementation more closely with the TSGo version and simplifies diagnostics that need to detect whether code is inside an Effect generator.