Regression: TypeScript with Yarn PnP configuration not working in Zed v0.154.2

[Brayan233]

Check for existing issues

• Completed

Describe the bug / provide steps to reproduce it

After upgrading to Zed v0.154.2, the TypeScript Yarn Plug'n'Play (PnP) configuration in local project settings (.zed/settings.json) stopped working. This setup was functional in Zed v0.153.7, but the recent update seems to have reverted the fix, causing the language server to ignore the local project settings.

Here is the local settings configuration that is not working:

{
  "lsp": {
    "vtsls": {
      "initialization_options": {
        "typescript": {
          "tsdk": ".yarn/sdks/typescript/lib"
        },
        "vtsls": {
          "autoUseWorkspaceTsdk": true
        }
      }
    }
  }
}

Steps to Reproduce:

1. Upgrade to Zed v0.154.2.
2. In the local project folder, create or update .zed/settings.json with the following configuration:

{
  "lsp": {
    "vtsls": {
      "initialization_options": {
        "typescript": {
          "tsdk": ".yarn/sdks/typescript/lib"
        },
        "vtsls": {
          "autoUseWorkspaceTsdk": true
        }
      }
    }
  }
}

3. Start the editor and observe the behavior of the language server.

Expected Behavior:

The language server should pick up the configuration from the local project's .zed/settings.json and correctly use the specified TypeScript SDK path.

Actual Behavior:

The language server ignores the local .zed/settings.json settings. This results in the failure of the expected functionality in the project environment.

Additional Notes:

• Rolling back to Zed v0.153.7 restores the expected functionality.
• It appears that the change introduced in Correctly merge settings for vtsls #17657 was reverted, causing this regression.

Related issues

• Configuring TypeScript with Yarn PnP in Zed Editor: Global vs. Local Settings #17046

Environment

Zed: v0.154.2 (Zed)
OS: macOS 15.0.0
Memory: 16 GiB
Architecture: x86_64

If applicable, add mockups / screenshots to help explain present your vision of the feature

No response

If applicable, attach your Zed.log file to this issue.

No response

[ai212983]

Any update on this? This is a showstopper for me, as it totally breaks TypeScript projects with Yarn PnP.

[dimasd-angga]

any update on this ? i cannot use ZED for my project :(

[noverby]

Any workarounds for this?

[akeating]

Rolling back to Zed v0.153.7 restores the expected functionality

Also add "auto_update": false, to your settings to avoid the inconvenience of zed immediately trying to upgrade again.

[ZayneLiu]

Had the a similar issue with vtsls config not working properly, I was using the initialization_options key to pass the config, but it stopped working for me couple months back.

Just had a look again on their doc here, I think they've changed the key in the vtsls config object from initialization_options to settings.

Anyway, changing to settings seems to work for me. So maybe give it a try.

"lsp": {
  "vtsls": {
    "settings": {
      "typescript": {
        "preferences": {
          "importModuleSpecifier": "non-relative"
        }
      }
    }
  }
}

[raska-vilem]

Hi, thank you @ZayneLiu, your solution works!

Someone should update the documentation to reflect this.

[cu8code]

hey @ZayneLiu solution did not solve this! also in vtsls I could not find option called importModuleSpecifier did anyone else have the same problem?

[cu8code]

hey I got it working!

  "lsp": {
    "vtsls": {
      "settings": {
        "typescript": {
          "tsdk": "~/.local/share/pnpm/global/5/node_modules/typescript/bin"
        }
      }
    }
  }

global install typescript-language-server
get the exact path I had to rename a file called tsserver to tsserver.js

Give a thumbs up its will heal my sole and make my 45 min worth it!

[ZayneLiu]

hey @ZayneLiu solution did not solve this! also in vtsls I could not find option called importModuleSpecifier did anyone else have the same problem?

@cu8code

importModuleSpecifier is here in the schema.

My use case is not the same as stated in the issue, but the solution applies, as long as the config passed matches vtsls schema.

[cu8code]

Thx @ZayneLiu I missed it; I don't know why It did not work! my solution is so much annoying!

[xcrap]

Having the same issues all the suddenly, not even using typescript in some projects where this appears.