Intellisense / type checking stopped working in v0.22.4

[Soresu]

• I have searched through existing issues
• I have read through docs
• I have read FAQ

Info

• Platform: Windows 10 x64
• Vetur version: 0.22.4
• VS Code version: 1.38.1
• Already reinstalled Visual Studio Code, Vetur
• Happens on multiple PC
• Tried to remove other plugins

Problem

Intellisense stopped working properly in Vue files. Although it works in the first opened vue file or if it was opened in the previous session.
Downgrading to Vetur 0.22.3 fixed the issue.

Reproducible Case

1. Close all tabs in the current project
2. Close and open Visual Studio Code
3. Open a vue file
4. Wait until the plugins are loaded
5. Hovering over/Ctrl+space at imported objects, variables doesn't show any info
6. Close and open Visual Studio Code
7. Intellisense works in the previously opened file

[borradaniele]

Same here, linking between files does not work with cmd and intellisense does not shows up, already tried to uninstall and reinstall.
Seems like occasionally it starts working again for some times and then stops again, not sure about the events chain that causes this tho.

Platform: Mac OS Mojave 10.14.6
VS Code version: 1.38.1
Vetur version: 0.22.4

If you need more info or log let me know.

[alexsasharegan]

Same on Linux.

Vetur: 0.22.4

VSCode Stats:
Version: 1.38.1
Commit: b37e54c98e1a74ba89e03073e5a3761284e3ffb0
Date: 2019-09-11T13:30:08.229Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Linux x64 5.0.0-31-generic

[yoyo930021]

#1317 (comment)
+1

[Sheng-Long]

Same issue for me, although it always seems to work in at least one file, but not the others

[hkk2018]

+1

[matthew-ch]

Similar issue for my project using typescript.

VSCode version: 1.39.0
OS: macOS Catalina 10.15
Vetur version: 0.22.4

Downgrading to 0.22.3 works.

[Ttou]

+1

[sppera]

+1

• Platform: Linux fedora 5.2.18-200.fc30.x86_64
• Vetur version: 0.22.4
• VS Code version: 1.39.1

[wfischer42]

Similar issue.
Specifically, TypeScript errors only show up in the first file I open after launching VSCode.
This was true using both TSLint Vue and ESLint to validate.

Downgrading to 0.22.3 worked for me too.

[SunshowerC]

same here.
Platform: Mac
Vetur version: 0.22.4

[imakan]

Downgrading to 0.22.3 worked for me

[Yancy1028]

my english is bad,but I know how to reproduce the problem.
in my new application,
1st use any "*.vue" file in "router.ts",and close all opened vue file,
2nd resert VSCode,and then open a normal vue file,that's ok,
3rd open any one vue file is "router.ts" used.that is not work.

it's look like ,vue file is import on other *".ts" file,vue IntelliSense not work.

[amirafzali]

Platform: Mac
Vetur version: 0.22.4

Only one file has working intellisense at a given time. Language server keeps crashing.
Downgrading to 0.22.3 fixed the problem.

[rchl]

Guys, there is no need for more confirmations. Just use the reaction icon if you need to say "me too"

[tomasbjerre]

Same here. It works for a while after reinstall.
Workaround: CTRL-P and type: > Reinstall Extension and pick Vetur.

[petternordholm]

Hi!

Did some debugging on this issue. AFAIK, the problem is related to:
javascript.ts:languageServiceIncludesFile

This method is called with the .vue file and return false. This will bypass validation, hovering, etc. and return an empty result.

For instance:

    doValidation(doc: TextDocument): Diagnostic[] {
      const { scriptDoc, service } = updateCurrentVueTextDocument(doc);
      if (!languageServiceIncludesFile(service, doc.uri)) {
        return [];
      }

In our tsconfig.json, we are not including vue file since these will be pulled in by the compiler anyway when our entry point ts files are compiled.

So,

export function languageServiceIncludesFile(ls: ts.LanguageService, documentUri: string): boolean {
  const filePaths = ls.getProgram()!.getRootFileNames();
  const filePath = getFilePath(documentUri);
  const found = filePaths.includes(filePath);
  return found;
}

filePaths will not contain our vue files, only ts files, and the method will return false.

[yoyo930021]

Hi!

Did some debugging on this issue. AFAIK, the problem is related to:
javascript.ts:languageServiceIncludesFile

This method is called with the .vue file and return false. This will bypass validation, hovering, etc. and return an empty result.

For instance:

    doValidation(doc: TextDocument): Diagnostic[] {
      const { scriptDoc, service } = updateCurrentVueTextDocument(doc);
      if (!languageServiceIncludesFile(service, doc.uri)) {
        return [];
      }

In our tsconfig.json, we are not including vue file since these will be pulled in by the compiler anyway when our entry point ts files are compiled.

So,

export function languageServiceIncludesFile(ls: ts.LanguageService, documentUri: string): boolean {
  const filePaths = ls.getProgram()!.getRootFileNames();
  const filePath = getFilePath(documentUri);
  const found = filePaths.includes(filePath);
  return found;
}

filePaths will not contain our vue files, only ts files, and the method will return false.

#1450 PR will fixed.

[petternordholm]

Kudos @yoyo930021 .. Great work! Hope we can get this PR merged ASAP!

It is driving me crazy. I will apply your changes on my local VLS

[josh-hemphill]

I want to make sure this is my only issue, did this also break all emmet/bracket-closing functions as well?

[tomasbjerre]

If anyone wants to install a previous version, you can install it like this:

[octref]

Should be fixed in 0.22.5. Thanks to @yoyo930021 for fixing it! Sorry I had been traveling and just catching up with notifications.

[GordonBlahut]

0.22.5 still doesn't fix this for me. Downgrading to 0.22.3 works.

Windows 10 x64, VS Code 1.39.2
Tried uninstalling Vetur, deleting from extensions directory and reinstalling.

[octref]

@GordonBlahut Does it reproduce on the sample project? https://github.com/octref/veturpack
If not, can you open a new bug report with reproducible steps?

[douglasg14b]

I'm also having this issue, v0.22.4 & 0.22.5 both have this issue for me.

Manually downgrading to v0.22.3 resolves it.

[douglasg14b]

Why is the issue closed?

[Neme12]

I'm still encountering this issue after upgrading to 0.22.5. In fact it no longer works even in the first opened file.

[matthew-ch]

For me version 0.22.5 works, both in ts and non-ts projects.

[deankinane]

InelliSense now completely broken in 0.22.5.
Doesn't work in first open file or file opened from previous session.

Have tested both TS and JS and neither work.

Downgrading to 0.22.4 fixes the issue for the first opened file.

Downgrading to 0.22.3 fixes the issue for all files.

Environment details:
VS Code: 1.39.2
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.17134

[Soresu]

The new 0.22.5 still has the problem. Moreover, step 7 of the reproducible case is now broken too.

[yoyo930021]

I think to have another problem causes on this issue.
Maybe #1469

If (use windows OS and broken) {
    pick +1 reaction.
} else {
    pick -1 reaction.
}

@Soresu @Neme12 @douglasg14b @GordonBlahut

[yoyo930021]

I think have an error fix in #1450.

I fix it on #1472.
Have anyone can verify it?

[praveenpuglia]

I don't know. I used 0.22.5 for most part of the day today. Haven't seen problems. Help me see the problem?

[petternordholm]

I don't know. I used 0.22.5 for most part of the day today. Haven't seen problems. Help me see the problem?

@praveenpuglia I think the problem is related to windows and windows filepaths. Are you running VSCode on linux or mac ?

[praveenpuglia]

macOS Catalina - 10.15

[octref]

Fix for Windows is released on 0.22.6.

[Soresu]

@octref Seems like 0.22.6 fixed the issue.

[lzinga]

I believe I am still getting this issue. I have been able to get the import intellisense paths to work by using this post on reddit. However when I try to access anything from the imported file there is no intellisense.
Inside the imported file the following exists.

import axios from 'axios'

export const test = {
	async get(id) {
		// ..
	}
}

Intellisense doesn't even exist for any Vue elements either. I am at a complete halt in my development because of this issue that I can't seem to get past. I am somewhat new to dealing with js but have been programming for quite a few years now and have been frustrated for over a week now.

[yoyo930021]

@lzinga please give more info for this.
Create new issue, and use issue template.

[Niekvdm]

Issue arrised again in 0.23.0 see #1589

[ykamal]

Bumping this. Same problem. Suddenly stopped working.
Version: 1.45.0 (user setup)
Commit: d69a79b73808559a91206d73d7717ff5f798f23c
Date: 2020-05-07T16:18:48.860Z
Electron: 7.2.4
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363
Installing/Reinstalling Vetur didn't help.