Skip to content

Vue LSP not providing autocomplete when project is opened directly from WSL2 filesystem on Windows #85

@gian881

Description

@gian881

Environment

  • OS: Windows 10
  • WSL2 Distro: Arch Linux
  • Zed version: 0.217.3
  • Vue extension version: 0.2.10

Description

I’m experiencing a very strange issue with the Vue LSP when working with projects located inside the WSL2 filesystem.

When opening a Vue project directly from the Linux filesystem (inside WSL2) using a Linux terminal, the Vue language server does not provide any autocomplete in <script> blocks, and also does not provide prop autocomplete in templates — even though other LSP features work.

However, if the same project is opened from the Windows filesystem, everything works perfectly.

What works

  • Go to definition works
  • Hover type information works
  • Auto-import of components in templates works

What does not work

  • No autocomplete in <script> blocks
  • No prop autocomplete for components inside templates

Expected Behavior

When opening a Vue project located inside the WSL2 filesystem, Zed should initialize the Vue language server normally and provide the same features available when opening projects from the Windows filesystem, including:

  • Autocomplete inside <script> blocks
  • Prop autocomplete for components in templates
  • Automatic and consistent Vue LSP initialization, even if a .vue file is already open when Zed starts

The behavior should be consistent regardless of:

  • Whether Zed is launched from a Windows or Linux terminal
  • Whether the project is located on the Windows filesystem or inside the WSL filesystem

Observed behavior

1. Opening from Windows filesystem

When I open the project located on the Windows filesystem using the Windows terminal, everything works normally.

2. Opening from WSL filesystem

When I open the project located inside the WSL Linux filesystem using a Linux terminal, the problem appears:

  • No autocomplete in <script>
  • No prop autocomplete in templates

3. “Priming” Zed fixes the issue

If I:

  • First open Zed from the Windows filesystem (Windows terminal),
  • And then open the WSL project via Linux terminal,

the problem does not happen anymore — everything works.

Same if:

  • I open Zed in any Windows filesystem folder
  • Then use Open Recent to open the WSL project — everything works.

4. Vue LSP not starting if a .vue file is already open

When I open Zed directly inside a WSL filesystem project and there is already a .vue file open:

  • The Vue LSP does not start at all.
  • It only starts if I open the project with no file opened and then manually open a .vue file.

On the Windows filesystem, this behavior does not happen — the Vue LSP always starts correctly.

Reproduction videos

Video showing the main issue happening

zed.vue.bug.mp4

Video showing Zed opened from Windows then opening the WSL project working correctly

opening.project.via.recents.mp4

Video showing Vue LSP not starting when .vue is already open

lsp.not.loading.on.open.file.mp4

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions