build(deps-dev): bump @effect/language-service from 0.63.2 to 0.64.1

[dependabot]

Bumps @effect/language-service from 0.63.2 to 0.64.1.

Release notes

Sourced from @​effect/language-service's releases.

v0.64.1

Patch Changes

• #568 477271d Thanks @​mattiamanzati! - Fix auto-import with namespace import packages generating malformed code when the identifier is at the beginning of the file.

  When using namespaceImportPackages configuration and auto-completing an export like isAnyKeyword from effect/SchemaAST, the code was incorrectly generated as:

  SchemaAST.import * as SchemaAST from "effect/SchemaAST";

  Instead of the expected:

  import * as SchemaAST from "effect/SchemaAST";
  SchemaAST.isAnyKeyword;

  The fix ensures the import statement is added before the namespace prefix when both changes target position 0.

v0.64.0

Minor Changes

• #567 dcb3fe5 Thanks @​mattiamanzati! - Added new diagnostic catchAllToMapError that suggests using Effect.mapError instead of Effect.catchAll + Effect.fail when the callback only wraps the error.

  Before:

  Effect.catchAll((cause) => Effect.fail(new MyError(cause)));

  After:

  Effect.mapError((cause) => new MyError(cause));

  The diagnostic includes a quick fix that automatically transforms the code.

• #555 0424000 Thanks @​mattiamanzati! - Add globalErrorInEffectCatch diagnostic to detect global Error types in catch callbacks

  This new diagnostic warns when catch callbacks in Effect.tryPromise, Effect.try, Effect.tryMap, or Effect.tryMapPromise return the global Error type instead of typed errors.

  Using the global Error type in Effect failures is not recommended as they can get merged together, making it harder to distinguish between different error cases. Instead, it's better to use tagged errors (like Data.TaggedError) or custom errors with discriminator properties to enable proper type checking and error handling.

  Example of code that triggers the diagnostic:

  Effect.tryPromise({

... (truncated)

Changelog

Sourced from @​effect/language-service's changelog.

0.64.1

Patch Changes

• #568 477271d Thanks @​mattiamanzati! - Fix auto-import with namespace import packages generating malformed code when the identifier is at the beginning of the file.

  When using namespaceImportPackages configuration and auto-completing an export like isAnyKeyword from effect/SchemaAST, the code was incorrectly generated as:

  SchemaAST.import * as SchemaAST from "effect/SchemaAST";

  Instead of the expected:

  import * as SchemaAST from "effect/SchemaAST";
  SchemaAST.isAnyKeyword;

  The fix ensures the import statement is added before the namespace prefix when both changes target position 0.

0.64.0

Minor Changes

• #567 dcb3fe5 Thanks @​mattiamanzati! - Added new diagnostic catchAllToMapError that suggests using Effect.mapError instead of Effect.catchAll + Effect.fail when the callback only wraps the error.

  Before:

  Effect.catchAll((cause) => Effect.fail(new MyError(cause)));

  After:

  Effect.mapError((cause) => new MyError(cause));

  The diagnostic includes a quick fix that automatically transforms the code.

• #555 0424000 Thanks @​mattiamanzati! - Add globalErrorInEffectCatch diagnostic to detect global Error types in catch callbacks

  This new diagnostic warns when catch callbacks in Effect.tryPromise, Effect.try, Effect.tryMap, or Effect.tryMapPromise return the global Error type instead of typed errors.

  Using the global Error type in Effect failures is not recommended as they can get merged together, making it harder to distinguish between different error cases. Instead, it's better to use tagged errors (like Data.TaggedError) or custom errors with discriminator properties to enable proper type checking and error handling.

  Example of code that triggers the diagnostic:

... (truncated)

Commits

• 2b66b3b Version Packages (#569)
• 477271d fix: correct auto-import order for namespace imports at file start (#568)
• b4c6d19 Version Packages (#556)
• dcb3fe5 feat: add catchAllToMapError diagnostic (#567)
• 036c491 Simplify global Error diagnostic messages (#566)
• 2274aef fix: support namespace imports for unnecessaryPipe diagnostic (#565)
• 57d5af2 Add overview CLI command (#562)
• 75a480e Improve unsupportedServiceAccessors diagnostic message for Effect.Tag (#560)
• c3b3bd3 Add descriptions to CLI commands (#561)
• 4c1f809 fix: improve Layer Magic ordering by considering both provides and requires c...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)