Intellisense/ AutoComplete Not Working in VS Code

[TeddyPerkins]

Current behavior:

Intellisense/ AutoComplete Not Working in VS Code.

Desired behavior:

Intellisense/ AutoComplete Should Work in VS Code.

Problem:

I have been working on this problem for 8+ hours. I have tried adding /// ..., jsconfig.json, tsconfig.json, duplicating it on cypress folder and combination of these. Autocomplete works on Jetbrain's Webstorm browser.

Hacky Solution:

1. So I took backup(just in case) and deleted 'Code' folder located in "C:\Users\(UserName)\AppData\Roaming\Code" in Windows.

2. Follow Official Docs
   Or Follow what I did:
   I created 'tsconfig.json'(although I use .js file) under 'cypress' folder and pasted this:

{
	"compilerOptions": {
			"allowJs": true,
			"types": ["cypress"]
	},
	"include": ["**/*.*"]
}

So I dont have to use /// <reference types="Cypress" /> in every cypress file.

3. Reloaded VS Code and autocomplete started working!
   [I also deleted extension folder and reverted backup - No change - So not necessary to delete extension folders]

I use windows 7 and dont know if it should be done in mac etc. Take backup and dont blame me if you dont know what you are doing. Or just install Webstorm(Jetbrain) and test if autocomplete works and if it works then proceed to the hacky solution I mentioned.

DONT CLOSE THIS ISSUE:

The solutions is hacky and should be solved by fixing Cypress, not deleting VSCode files!

[jennifer-shehane]

I'm not sure why deleting VSCode app data was necessary in your case, but we've never had this issue reported before, so it seems isolated to something with your config/env and not Cypress specifically. I'm not sure how this is a Cypress issue exactly and what we could even do about your VSCode AppData.

[TeddyPerkins]

https://stackoverflow.com/questions/52434223/lost-intellisense-for-cypress-in-visual-studio-code
Yu Jia had the same problem, does not works on VS Code but works on Web Storm...

That's why I had to delete App Data Folder, it happens but to very few people. My guess is some other intellisense or settings for it interfered with Cypress's Autocomplete settings...

[k2589]

I also got an issue - yesterday autocomplete was working, today is not working)

[k2589]

I also got an issue - yesterday autocomplete was working, today is not working)

sorry, it was related to linter issues. fixed with:

/* eslint-disable */ 
/// <reference types="cypress" />
/* eslint-enable */

[mrmowji]

I have the same problem.

1. Using /// <reference types="cypress" /> per file works but it's not a good solution.
2. Using tsconfig.json as described on the docs works, but my project is not a TypeScript project and I got a repeating error using this config file.
3. Using jsconfig.json doesn't work. I restart the TS Server with every change I make into this file. Nothing works. I also tried "typeAcquisition": { "include": ["cypress"] }; doesn't work either.

[iamgollum]

My team has a similar problem working with custom commands in VSCode as @mrmowji. CC: @timsand. System: Macbook Pro - Mojave.

1. Working with only JS files except for our typescript definition file (see 2)
2. Added index.d.ts under support/ for our custom commands with
   /// <reference types="cypress" /> at the top in order to avoid having to copy the reference comment across spec files.
3. Using jsconfig.json under project root with an includes for support/ works correctly until we have to start the react server using CRA and it fails.
4. Using tsconfig.json doesn't work at all as described in the docs. We tried adding it in the root of our project and in cypress (w/ paths adjusted accordingly). However @bahmutov tsconfig.json works only for cypress, not custom commands after swapping out '.ts' for '.js', so it seems the 'node' option fixes it. We also tried adding the type roots to point to support but to no avail. When we run start with CRA, it gets augmented for typescript and cypress based on the templates "best practice fixes" but it doesn't do anything to improve or negate it.

The team is going back to try no. 3 again since it maybe a CRA issue.
[UPDATE] using *.* in includes fixes the tsconfig.json.
however now Cypress doesn't run at all but the app works (we are trying to avoid this...)
We are also playing around with what is mentioned here even though this is not the issue we are facing: https://www.cypress.io/blog/2019/05/13/code-create-react-app-v3-and-its-cypress-tests-using-typescript/ .. noEmit: false doesn't work and SKIP_FLIGHT_PRECHECKS is generally an anti-pattern :(

Conclusion
Team is opting to use jsconfig for cypress core and then the jsdoc type references for the support/ at this time

[jennifer-shehane]

We'll be moving this issue to our docs to improve the documentation, as this is outside the scope of the product itself. Our documentation is open source and contributions are welcome.