microsoft / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
163.51k stars 28.99k forks source link

JS suggestion Intellisense not working #97163

Closed ThomasLai1991 closed 4 years ago

ThomasLai1991 commented 4 years ago

Version of VS Code image

Your operating system windows 7 ultimate SP1

List of extensions that you have installed image

I've tried disabled all extension then restart VScode, still not working.

Reproducible steps (1... 2... 3...) that cause the issue

1 $ mkdir toDoList create a directory 2 $ cd toDoList move into the created directory 3 $ node init initialize package.json 4 $ npm i express install express 5 $ touch app.js create a js file 6 try to type something to trigger intellisense (say setTimeOut or setInterval or just a dot)

What you expected to see, versus what you actually saw I expected to see intellisense pop up telling me any suggested methods or variables I saw no suggestions in intellisense but only the recorded names of what I typed before

Images, animations, or a link to a video showing the issue occurring GIF 2020-5-8 14-02-26

for comparison below is what happen on my another computer everything works fine with similar settings. GIF 8-05-2020 6-12-07 p m

A code snippet that demonstrates the issue or a link to a code repository the developers can easily pull down to recreate the issue locally

https://github.com/ThomasLai1991/ReportIntellisenseIssue

Errors from the Dev Tools Console (open from the menu: Help > Toggle Developer Tools)

image

image

Hmm...I just noticed this error from Dev Tools Console, I suspect my error has something to do with this. This setting.json I did not touch manually before as I am not an expert and know nothing much about it but might cause by something else when I learn about bable and node, and I don't know how to fix it as well

But there is no suggestion at all, even a simple setTimeOut or setInterval is not there. My vscode on my another computer is working fine with identical settings.

I've tried to uninstall and reinstall vscode with the lastest version, no luck.

image

image

mjbvz commented 4 years ago

Please fill out the issue template. For example, what VS Code version and OS are you on?

/needsMoreInfo

ThomasLai1991 commented 4 years ago

Thank you very much for your response, I have updated the information according to the guidelines, thanks.

On Fri, 8 May 2020 at 04:06, Matt Bierner notifications@github.com wrote:

Please fill out the issue template. For example, what VS Code version and OS are you on?

/needsMoreInfo

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/microsoft/vscode/issues/97163#issuecomment-625469526, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFKUF2OH5RD7TFXRONA4LX3RQMIDXANCNFSM4M3OWDRQ .

ThomasLai1991 commented 4 years ago

Please fill out the issue template. For example, what VS Code version and OS are you on?

/needsMoreInfo

Please fill out the issue template. For example, what VS Code version and OS are you on?

/needsMoreInfo

Thank you sir, I've update more info.

I now highly suspect this error has something to do with the setting.json as shown in the screenshot of "Toggle Developer Tools" But I still don't know what is the proper value for that setting of 'javascript':'babel-node' Would you please see to it? thanks

mjbvz commented 4 years ago

Does this reproduce in the latest VS Code insiders build with all extensions disabled?

ThomasLai1991 commented 4 years ago

Does this reproduce in the latest VS Code insiders build with all extensions disabled?

Hi Sir, No it does not reproduce in the latest VS code insider.

what I found is that when I comment out this line in my settings.json in my normal vscode verson: "javascript": "babel-node", the bug is gone. And because the insider build use a different settings.json, the insider build does not have the same bug.

But would you mind to tell me what is the proper way to address the bug cause by that line instead of simply comment it out? Any materials to read to guide me on the settings? I don't see why babel-node is going to be a problem for JavaScript suggestion. Thank you so much, again.

mjbvz commented 4 years ago

Where exactly is "javascript": "babel-node", used in your settings json? Can you share the full setting name?

ThomasLai1991 commented 4 years ago
{
    "liveServer.settings.donotShowInfoMsg": true,
    "open-php-html-js-in-browser.selectedBrowser": "Chrome",
    "javascript": "babel-node",
    "[javascript]": {
        "editor.defaultFormatter": "bysabi.prettier-vscode-semistandard"

    },
    "javascript.suggest.completeFunctionCalls": true,
    "emmet.showSuggestionsAsSnippets": true,
    "editor.suggest.filterGraceful": false,
    "editor.quickSuggestions": true,
    "editor.lineNumbers": "on",
    "vim.insertModeKeyBindings": [
        {
            "before":["<space>","<space>"],
            "after":["<Esc>"]
        }
    ],
    "editor.cursorSurroundingLines": 15
}

this is the whole of my settings.json. As far as as I remember I only manually set the vim settings only, didn't touch too much on any other settings, basically keep everything default. Thank you.

mjbvz commented 4 years ago

It sounds like this issue is caused by one of you extensions. I don't know which extension contributes "javascript": "babel-node", but since removing that setting fixes intellisense, that extension is likely the cause.

Once you find which extension causes this, please file an issue against them