Vue "Go to definition" no longer works

[amir20]

Check for existing issues

• Completed

Describe the bug / provide steps to reproduce it

I thought I was doing something wrong, but started recently. Zed's command+click or right click to go to definition no longer works in Vue files.

I have tested with a brand new project with pnpm create vite and then use Vue as template.

Note that react using pnpm create vite still works.

Environment

Zed: v0.148.1 (Zed)
OS: macOS 14.6.1
Memory: 16 GiB
Architecture: aarch64

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

Zed.mp4

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

Zed.log

[amir20]

Note in the video the first window is a React example and second is the broken experience in Vue.

[fazulk]

related to this issue #14723

[amir20]

That's funny because autocomplete works me. 🤷🏼‍♂️

[d1y]

I think you can provide the logs. I suspect that you may have installed other plugins?

[amir20]

Updated with logs. Attached screenshot with extensions.

This used to work. But now it is broken all my vue projects so I don't think it's related to something I am doing.

[d1y]

@amir20 I have also reproduced this issue and found that it seems to be caused by tailwindcss lsp(maybbbbe?)
Please try disabling it
After disabling it, I can work

{
	// disable tailwindcss
	"language_servers": ["!eslint", "!typescript-language-server", "!tailwindcss-language-server", "..."],
}

Screen.Recording.2024-08-20.at.01.30.08.mov

[amir20]

Confirmed. "language_servers": ["!tailwindcss-language-server"] fixes the issue. Now the problem is, I do use Tailwind too.

Is this related to #14723? It doesn't seem like it.

[vknowles-rv]

I downgraded back to 1.147.2 and go to/code navigation started working again.

I also disabled auto updating as I lost half a day due to this

[amir20]

Yea I think I misspoke. Even with tailwind disabled I see this happening. I am wondering if some extension got auto updated.

I also lost a lot of time. Going back to Vscode for a while.

[icarusgk]

Disabling the Tailwind extension with "language_servers": ["!tailwindcss-language-server"]
worked for me too.

[danulqua]

I don't even have the Tailwind extension, so it doesn't work even with "language_servers": ["!tailwindcss-language-server"]

[icarusgk]

@danulqua Try adding the three dots at the end "language_servers": ["!tailwindcss-language-server", "..."]

[flootr]

I downgraded back to 1.147.2 and go to/code navigation started working again.

Downgrading worked for me, too. Setting "language_servers": ["!tailwindcss-language-server", "..."] did not, unfortunately.

[danulqua]

@icarusgk didn't work. Go to definition doesn't work at all everywhere, in <template> and in <script>.

[SomeoneToIgnore]

I have something that looks like a fix, waiting for the review/confirmation: #16654

Meanwhile, using

"languages": {
  "Vue.js": {
    // this is a new line
    "language_servers": ["vue-language-server", "..."],
    "prettier": {
      "allowed": true
    }
  },
}

could help as a workaround.

[icarusgk]

Thank you @SomeoneToIgnore, That works! 🚀

[amir20]

Thank you @SomeoneToIgnore for the great work.

[misaelvillaverde]

Hello, same thing with Astro.

Used:

  "languages": {
    "Astro": {
      "language_servers": ["astro-language-server"]
    },
    ...
  }

[SomeoneToIgnore]

Astro seems to have a single language server supported, so this seems a bit unrelated: the current workaround forces a certain, primary, language server to be used first, e.g. :

    "language_servers": ["vue-language-server", "..."],

which is not applicable to a single entry, really.

[misaelvillaverde]

I understand, but the "go to definition" doesn't work in astro files (at least on my end) without explicitly setting that up.