@effect/language-service

language-service

This package implements a TypeScript language service plugin that allows additional refactors and diagnostics with your VSCode editor (or any editor that supports TypeScript's LSP).

Installation

• npm install @effect/language-service --save-dev in your project
• Inside your tsconfig.json, you should add the plugin configuration as follows:

{
  "compilerOptions": {
    "plugins": [
      // ... other LSPs (if any) and as last
      {
        "name": "@effect/language-service"
      }
    ]
  }
}

• Ensure that you have installed TypeScript locally in your project and set your editor to use your workspace TypeScript version.

  • In VSCode you can do this by pressing "F1" and typing "TypeScript: Select TypeScript version". Then select "Use workspace version". If that option does not appear, TypeScript is not installed locally in your node_modules.
  • In JetBrains you may have to disable the Vue language service, and choose the workspace version of TypeScript in the settings from the dropdown.
  • In NVim with nvim-vtsls you should refer to how to enable TypeScript plugins in vtsls
  • In Emacs, additional steps are required to enable LSPs, step by step instructions can be found here

And you're done! You'll now be able to use a set of refactors and diagnostics that target Effect!

Provided functionalities

Quickinfo

• Show the extended type of the current Effect
• Hovering yield* of Effect.gen will show the Effect type parameters
• Hovering a variable assignment of a type Layer, will show info on how each service got involved
• Hovering a layer, will attempt to produce a graph

Diagnostics

• Better error readability when you're missing errors or service types in your Effect definitions
• Floating Effects that are not yielded or run
• Wrong usage of yield inside Effect.gen
• Multiple versions of Effect in your project
• Warn on leaking requirements in Effect services
• Warn on Scope as requirement of a Layer
• Warn on subsequent Effect.provide anti-pattern
• Unnecessary usages of Effect.gen or pipe()
• Warn when importing from a barrel file instead of from the module directly
• Warn on usage of try/catch inside Effect.gen and family
• Detect unnecessary pipe chains like X.pipe(Y).pipe(Z)

Completions

• Autocomplete 'Self' in Effect.Service, Context.Tag, Schema.TaggedClass, Schema.TaggedRequest and family
• Autocomplete Effect.gen with function*(){}
• Autocomplete Effect.fn with the span name given by the exported member
• Completions for DurationInput string millis/seconds/etc...
• Allow to configure packages to be imported with namespace style import * as Effect from "effect"
• Suggest brand when using Schema.brand
• Effect comment directives

Refactors

• Transform an async function definition, into an Effect by using Effect.gen.
• Transform an async function definition, into an Effect by using Effect.gen, and generating a tagged error for each promise call.
• Transform a function returning an Effect.gen into a Effect.fn
• Implement Service accessors in an Effect.Service or Context.Tag declaration
• Function calls to pipe: Transform a set of function calls to a pipe() call.
• Pipe to datafirst: Transform a pipe() call into a series of datafirst function calls (where available).
• Toggle return type signature: With a single refactor, adds or removes type annotations from the definition.
• Remove unnecessary Effect.gen definitions that contains a single yield statement.
• Wrap an Effect expression with Effect.gen
• Toggle between pipe styles X.pipe(Y) and pipe(X, Y)

Miscellaneous

• "Go to definition" for RpcClient will resolve to the Rpc definition

Options

Few options can be provided alongside the initialization of the Language Service Plugin.

{
  "compilerOptions": {
    "plugins": [
      {
        "name": "@effect/language-service",
        "diagnostics": true, // controls Effect diagnostics (default: true)
        "diagnosticSeverity": { // allows to change per-rule default severity of the diagnostic in the whole project
          "floatingEffect": "warning" // example for a rule, allowed values are off,error,warning,message,suggestion
        },
        "quickinfo": true, // controls quickinfo over Effect (default: true)
        "completions": true, // controls Effect completions (default: true)
        "goto": true, // controls Effect goto references (default: true)
        "allowedDuplicatedPackages": [], // list of package names that have effect in peer dependencies and are allowed to be duplicated (default: [])
        "barrelImportPackages": [], // package names that should be preferred as imported from the top level barrel file (default: [])
        "namespaceImportPackages": [] // package names that should be preferred as imported with namespace imports e.g. ["effect", "@effect/*"] (default: [])
      }
    ]
  }
}

Why do diagnostics not appear at compile time?

TypeScript LSPs are loaded only while editing your files. That means that if you run tsc in your project, the plugin won't be loaded and you'll miss out on the Effect diagnostics.

HOWEVER, if you use ts-patch you can enable the transform as well to get the diagnostics also at compile time. Your tsconfig.json should look like this:

{
  "compilerOptions": {
    "plugins": [
      {
        "name": "@effect/language-service",
        "transform": "@effect/language-service/transform" // enables diagnostics at compile time when using ts-patch
      }
    ]
  }
}

To get diagnostics you need to install ts-patch which will make it possible to run tspc.

Running tspc in your project will now also run the plugin and give you the error diagnostics at compile time. Effect error diagnostics will be shown only after standard TypeScript diagnostics have been satisfied. Beware that setting noEmit will completely skip the effect diagnostics.

$ npx tspc
index.ts:3:1 - error TS3: Effect must be yielded or assigned to a variable.

3 Effect.succeed(1)
  ~~~~~~~~~~~~~~~~~

Found 1 error in index.ts:3 

Configuring diagnostics

You can either disable or change the severity of specific diagnostics by using comments in your code.

// @effect-diagnostics effect/floatingEffect:off
Effect.succeed(1); // This will not be reported as a floating effect

// @effect-diagnostics effect/floatingEffect:error
Effect.succeed(1); // This will be reported as a floating effect

or you can set the severity for the entire project in the global plugin configuration

{
  "compilerOptions": {
    "plugins": [
      {
        // ...
        "diagnosticSeverity": { // allows to change per-rule default severity of the diagnostic in the whole project
          "floatingEffect": "warning" // example for a rule, allowed values are off,error,warning,message,suggestion
        },
        // ...
      }
    ]
  }
}

Known gotchas

Svelte VSCode extension and SvelteKit

The Svelte LSP does not properly compose with other LSPs when using SvelteKit. So the Effect LSP should be loaded as last entry to ensure proper composition.

If you did not install the Svelte LSP into your local project but instead through the Svelte VSCode extension, we recommend instead to install it locally and add it as the first entry. That way it won't be applied by the VSCode extension.

Your tsconfig.json should look like this:

{
  "compilerOptions": {
    "plugins": [
      { "name": "typescript-svelte-plugin" },
      { "name": "@effect/language-service" }
    ]
  }
}