_From @hellopao on February 15, 2016 3:15_
I've upgraded the vs code to the latest version ,and the Salsa was enabled.
Now, the code intellisense does not work without an jsconfig.json file. but version 0.10.6 worked well.


_Copied from original issue: Microsoft/vscode#3017_
_From @meritozh on February 15, 2016 3:41_
Same issues. I hope Salsa can works without a jsconfig.json. How about contain a default jsconfig.json without manual creating one?
_From @nilshartmann on February 18, 2016 13:15_
In my case Intellisense (even with a jsconfig.json) only works for modules that have been required but not for modules that have been imported using ES6 import:

You can find my sample project here: https://github.com/nilshartmann/vsctest
My environment:
{
"compilerOptions": {
"target": "ES6"
},
"exclude": [
"node_modules"
]
}
Just noticed: Importing a module from my own project that uses ES6 export seems to work.
I'm not sure if this is the same problem or to better open a new Issue?
If you open a loose file, then we have no project context, so we're not pulling in the node.d.ts. That would explain the require("fs'"); not working in the loose file scenario above.
For the ES6 import case, this may be similar/related to #7076. I'll take a look at these together.
Verified the behavior is as expected in 'master' currently. Note that above for the statement import http from "http", this is a default import, you'll need to set "allowSyntheticDefaultImports": true for this to work, else instead use import * as http from "http" to import the CommonJS module as a namespace.
Still not working. I have the following. And even if I set "allowSyntheticDefaultImports": true still doesn't show any Intellisense.
Version 1.9.1
Commit f9d0c687ff2ea7aabd85fb9a43129117c0ecf519
Date 2017-02-08T23:44:55.542Z
Shell 1.4.6
Renderer 53.0.2785.143
Node 6.5.0
@Hosar this is an old issue. please file a new issue and provide enough information for us to be able to reproduce it.
So, whan that shit will be fixed? I've got same annoying issue. Hate this. ver 1.10.2
Most helpful comment
So, whan that shit will be fixed? I've got same annoying issue. Hate this. ver 1.10.2