chore(deps): update dependency @effect/language-service to ^0.80.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@effect/language-service	^0.77.0 → ^0.80.0

---

Release Notes

Effect-TS/language-service (@​effect/language-service)

v0.80.0

Compare Source

Minor Changes

• #​681 1017a54 Thanks @​mattiamanzati! - Generate a root schema.json for tsconfig.json plugin configuration, add typed Effect Language Service plugin options to that schema, and have effect-language-service setup add or remove the matching $schema entry automatically.

• #​679 3664197 Thanks @​mattiamanzati! - Add inline --lspconfig support to the effect-language-service diagnostics CLI command so diagnostics runs can override the project plugin configuration without editing tsconfig.json.

v0.79.0

Compare Source

Minor Changes

• #​671 6b9c378 Thanks @​mattiamanzati! - Add the extendsNativeError diagnostic to warn when classes directly extend the native Error constructor, including common local aliases such as const E = Error.

  This helps steer users toward tagged errors that preserve stronger typing in the Effect failure channel.

• #​678 0e9c11b Thanks @​mattiamanzati! - Generate the README diagnostics table from the diagnostic registry.

  Each diagnostic now declares:

  • whether it is fixable
  • which Effect versions it supports

  The generated table is checked in CI, and diagnostics tests verify that fixable matches the presence of non-suppression quick fixes.

• #​676 2f982d6 Thanks @​mattiamanzati! - Add the nodeBuiltinImport diagnostic to warn when importing Node.js built-in modules (fs, path, child_process) that have Effect-native counterparts in @effect/platform.

  This diagnostic covers ES module imports and top-level require() calls, matching both bare and node:-prefixed specifiers as well as subpath variants like fs/promises, path/posix, and path/win32. It defaults to severity off and provides no code fixes.

• #​673 f9e24df Thanks @​mattiamanzati! - Add plugin options to better control patched tsc behavior.

  ignoreEffectErrorsInTscExitCode allows Effect diagnostics reported as errors to be ignored for exit-code purposes, and skipDisabledOptimiziation keeps disabled diagnostics eligible for comment-based overrides when patch mode is active.

• #​674 54e8c16 Thanks @​mattiamanzati! - Add the serviceNotAsClass diagnostic to warn when ServiceMap.Service is used as a variable assignment instead of in a class declaration.

  Includes an auto-fix that converts const Config = ServiceMap.Service<Shape>("Config") to class Config extends ServiceMap.Service<Config, Shape>()("Config") {}.

Patch Changes

• #​675 d1f09c3 Thanks @​mattiamanzati! - Rename the skipDisabledOptimiziation plugin option to skipDisabledOptimization.

  Example:

  {
    "compilerOptions": {
      "plugins": [
        {
          "name": "@​effect/language-service",
          "skipDisabledOptimization": true
        }
      ]
    }
  }

v0.78.0

Compare Source

Minor Changes

• #​663 0e82d43 Thanks @​mattiamanzati! - Improve effectFnOpportunity inferred span naming for service-layer methods and align examples for Effect v4.

  The inferred span can now include service + method names (for example MyService.log) when the convertible function is a method inside a layer service object for strict supported patterns like:

  • Layer.succeed(Service)(...)
  • Layer.sync(Service)(...)
  • Layer.effect(Service)(Effect.gen(...))
  • Layer.effect(Service, Effect.gen(...))

  Also add Effect v4 diagnostics fixtures for:

  • effectFnOpportunity_inferred.ts
  • effectFnOpportunity_inferredLayer.ts

• #​669 a010a29 Thanks @​mattiamanzati! - Add a new effectInFailure diagnostic that warns when an Effect computation appears in the failure channel (E) of another Effect.

  The rule traverses Effect-typed expressions, unrolls union members of E, and reports when any member is itself a strict Effect type.

  It prefers innermost matches for nested cases (for example nested Effect.try in catch) to avoid noisy parent reports.

Patch Changes

• #​666 06b3a6c Thanks @​mattiamanzati! - Fix effectFnOpportunity inferred span naming for Layer.*(this, ...) patterns in class static members.

  When the inferred layer target is this, the diagnostic now uses the nearest enclosing class name (for example MyService) instead of the literal this token.

• #​665 a95a679 Thanks @​mattiamanzati! - Improve yield-based diagnostics and hover behavior by introducing effectYieldableType in TypeParser and using it in missingReturnYieldStar.

  • In Effect v4, yieldable values are recognized through asEffect() and mapped to Effect A/E/R.
  • In Effect v3, effectYieldableType falls back to standard effectType behavior.
  • missingReturnYieldStar now correctly handles yieldable values such as Option.none().
  • Hover support for yield* was updated to use yieldable parsing paths.

• #​664 934ef7e Thanks @​mattiamanzati! - Improve missingReturnYieldStar safety by targeting only expression statements with top-level yield* expressions and validating the enclosing Effect.gen scope via findEnclosingScopes.

  This avoids edge cases where nested or wrapped yield* expressions could be matched incorrectly.

• #​661 0f92686 Thanks @​mattiamanzati! - Update effect dependency to v4.0.0-beta.19 and fix compatibility issues:

  • Fix layerMagic refactor producing any types in Layer channels by replacing Array.partition (which now uses the v4 Filter.Filter API) with a native loop for boolean partition logic
  • Add v4 Layer type detection shortcut using "~effect/Layer" TypeId property, matching the pattern already used for Effect type detection
  • Mark Effect.filterMap as unchanged in the outdated API migration database since it was re-added in v4

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 83fbbde

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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