-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Javascript support broken? jsconfig.json's file directive is ignored, and intellisense doesn't work #2265
Comments
Oh, it works brilliantly on all platforms. |
Here's my
|
My problems remain. I've set up a repo showing the issue: https://github.com/manad777/vscodetest . I feel there is fundamental broken here, because I don't see what I'm doing anything different from you. What version of VSCode are you using? Here's a complete list of my issues on 0.10.5: FILE EXCLUSION
AUTOCOMPLETE/INTELLISENSEI ran the following commands: Yet, in app.js, I don't get autocomplete after _. If I press Ctrl+Space after the dot, I get "No suggestions". |
Strange on the autocomplete issue. I've seen something similar related to the default open-file limits in Mac & Linux. Can you post the results of this cmd: |
user1@ubuntu-webdev:~$ ulimit -a This is on Ubuntu 14.04. The issues you linked seem related to large amount of files in the project, or the name of directories in the path containing "js". I can reproduce it with nothing but a single app.js file in the root directory. |
I can confirm that Related issue (on the |
@manad777 I don't see the doc says it will "hide the files in the left pane". My understanding is that it only govern intelliSense. Am I wrong? |
+1 the same problem of lodash and _. Intellisense doesn't work. |
The misunderstanding is the sentence
In your jsconfig.json you define that only |
@egamma , thanks for clarifying that the explorer will always show everything regardless of configuration. It's not a bug, then. However, this issue shouldn't be closed yet. Neither of your suggestions to fix intellisense worked for me. I tried removing the files entry altogether, and I tried adding every single typings path I could think of. In both cases I restarted VSCode. And in both cases, I still had no intellisense in app.js. My example project has 2 new commits that you can peruse: https://github.com/manad777/vscodetest/commits/master |
I think |
@unioal thanks and agreed, the |
Thanks. @egamma . I just reconfirming that it is working too. 🍺 |
Thanks @egamma, |
Even after @egamma 's suggested jsconfig.json Intellisense wouldn't work. Then I deleted ~/.config/Code and tried again, and it worked. I've been using VS Code for a few months now, so it could have been caused by an artifact from an old version. |
The solution works with small projects but if it is a large project it doesn't work on VSCode version 1.3.1 @egamma do you have something related to it? I have read about it in the web and it seems to be a real issue, actually I made some changes excluding folders but it takes like 3 minutes trying to get the intellicense, and sometimes takes more time to do so. |
I used the first jsconfig.json example from https://code.visualstudio.com/Docs/languages/javascript in my project. According to the doc this config should only let app.js be visible in the left pane, but as you can see in the screenshot below it's not the case. I tried restarting Code, of course.
Similarly, Intellisense doesn't work at all. I installed typings using the tsd commands mentioned at https://code.visualstudio.com/Docs/runtimes/nodejs (they're visible in the screenshot), but autocomplete for commonjs modules is not working. A google search had people mentioning a tsd.d.ts file in the typings/ directory, but tsd didn't create one for me. I tried creating one by hand and populating it using the content with the entries below pointing at existing files, but autocomplete is still unavailable.
/// <reference path="node/node.d.ts" /> /// <reference path="lodash/lodash.d.ts" />
Does VS Code actually support Javascript, or did I completely misunderstand the doc?
The text was updated successfully, but these errors were encountered: