Vue LSP throws an error silently after a diagnostic error

[phsd0]

Vue - Official extension or vue-tsc version

3.2.4

VSCode version

Vue version

3.6.0-beta.4

TypeScript version

5.9.3

System Info

System:
    OS: macOS 26.0.1
    CPU: (14) arm64 Apple M3 Max
    Memory: 697.47 MB / 36.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.7.0 - /Users/foo/.nvm/versions/node/v24.7.0/bin/node
    npm: 11.5.1 - /Users/foo/.nvm/versions/node/v24.7.0/bin/npm
    pnpm: 10.15.0 - /Users/foo/Library/pnpm/pnpm
    bun: 1.3.0 - /Users/foo/Library/pnpm/bun
    Deno: 2.2.6 - /Users/foo/.deno/bin/deno
    Watchman: 2025.04.28.00 - /opt/homebrew/bin/watchman
  Browsers:
    Chrome: 144.0.7559.110
    Firefox: 139.0.4
    Safari: 26.0.1

package.json dependencies

Steps to reproduce

Don't know how to reproduce outside of zed but

• With Zed Vue language extension v0.3.0 installed create a new .vue file
• Add a basic Vue SFC scaffold for the composition API
• Add a new Div with an Emmet completion like ".test-class"
• Try to add an attribute to the Div like v-if="test"
• Try invoking another Emmet completion by typing '.' somewhere in the component template

What is expected?

that lsp don't crash

What is actually happening?

something causes the vue-language-server to crash silently with the following errors in the LSP logs:

/Users/foo/Library/Application Support/Zed/extensions/work/vue/node_modules/@vue/language-service/lib/plugins/vue-template.js:604
                                ...meta?.props.map(prop => [prop.name, prop]) ?? [],
                                              ^

TypeError: Cannot read properties of undefined (reading 'map')
    at Object.provideAttributes (/Users/foo/Library/Application Support/Zed/extensions/work/vue/node_modules/@vue/language-service/lib/plugins/vue-template.js:604:47)
    at /Users/foo/Library/Application Support/Zed/extensions/work/vue/node_modules/vscode-html-languageservice/lib/umd/services/htmlCompletion.js:212:30
    at Array.forEach (<anonymous>)
    at collectAttributeNameSuggestions (/Users/foo/Library/Application Support/Zed/extensions/work/vue/node_modules/vscode-html-languageservice/lib/umd/services/htmlCompletion.js:211:31)
    at HTMLCompletion._doComplete (/Users/foo/Library/Application Support/Zed/extensions/work/vue/node_modules/vscode-html-languageservice/lib/umd/services/htmlCompletion.js:408:44)
    at HTMLCompletion.doComplete (/Users/foo/Library/Application Support/Zed/extensions/work/vue/node_modules/vscode-html-languageservice/lib/umd/services/htmlCompletion.js:54:33)
    at HTMLCompletion.doComplete2 (/Users/foo/Library/Application Support/Zed/extensions/work/vue/node_modules/vscode-html-languageservice/lib/umd/services/htmlCompletion.js:41:33)
    at /Users/foo/Library/Application Support/Zed/extensions/work/vue/node_modules/volar-service-html/index.js:153:39
    at async runWithVueDataProvider (/Users/foo/Library/Application Support/Zed/extensions/work/vue/node_modules/@vue/language-service/lib/plugins/vue-template.js:501:30)
    at async Object.provideCompletionItems (/Users/foo/Library/Application Support/Zed/extensions/work/vue/node_modules/@vue/language-service/lib/plugins/vue-template.js:229:95)

Node.js v24.7.0

Link to minimal reproduction

No response

Any additional comments?

It seems to start happening after #5888 There is an issue in zed vue extension zed-extensions/vue#92. But maybe it caused on language server itself

[phsd0]

This fixes the issue. It seems like problem is that tsserver.getComponentMeta returns { type: 'noContent' } instead of undefined and then it causes meta.props.map to panic

function getTagData(tag) {
    let data = tagDataMap.get(tag);
    if (!data) {
        data = { attrs: [], meta: undefined };
        tagDataMap.set(tag, data);
        tasks.push((async () => {
            let meta = await tsserver.getComponentMeta(root.fileName, tag);
            //FIX: we should handle noContent type 
            if (meta?.type === 'noContent') {
              meta = undefined;
            }
            tagDataMap.set(tag, {
                attrs: await tsserver.getElementAttrs(root.fileName, tag) ?? [],
                meta,
            });
            version++;
        })());
    }
    return data;
}

[KazariEX]

I cannot find the string noContent in the TS lib, it is likely returned by the TS integration in the zed, and this issue needs to be resolved there.

[KazariEX]

https://github.com/typescript-language-server/typescript-language-server/blob/e91bd52a47c05ffd946e0abd27f242eb631b7604/src/tsServer/server.ts#L233

[phsd0]

https://github.com/typescript-language-server/typescript-language-server/blob/e91bd52a47c05ffd946e0abd27f242eb631b7604/src/tsServer/server.ts#L233

Even if vue ls doesn't care about tsserver but still vue can check if props are provided before accessing it
Doesn't this mean that vue language server should handle situation when .props isn't provided by tsserver?
maybe like if (meta?.props === undefined) { meta = undefined }

or when accessing meta?.props?.map(...) instead of meta?.props.map(...)