Editor prompts me to configure exclude

[elsigh]

• VSCode Version: 1.3.1
• OS Version: Mac OSX El Capitan 10.11.5

Steps to Reproduce:

1. Create a jsconfifg.json
   Here's mine:

{
    "compilerOptions": {
        "target": "ES6",
        "module": "es6"
    },
    "exclude": [
        "bower_components",
        "node_modules"
    ]
}

1. VSCode continues to prompt me to configure excludes
   

[kieferrm]

@elsigh just checking: Your file is jsconfig.json, correct?

[elsigh]

Indeed, jsconfig.json

When I click the bug it opens my jsoncfig.json file even.
But it is true that I have a lot of files in subdirectories there.

I'll see if it continues to happen as I'm pretty excited about using vscode going forward!

[jrieken]

@elsigh Can you hover over the message and let me know what the full reading is? There should be more folders

[elsigh]

But that's my primary project working directory ;) I don't want to exculde it.

[jrieken]

😄 that makes sense. The logic to compute the exclude suggestions isn't very smart and doesn't go deep. Meaning that when there is a large folder inside the ConsumerWeb folder we point to the parent only.

My question is if your project is actually that large or if this is caused by some dependencies or temp files (like ember serve easily creates 20mb of JS files)

[elsigh]

That folder is 10MB of actual code and some images but there are no temp things / build artifacts. Is there a way to exclude particular directories within a folder (e.g. **/img/)?

I do also have a number of things excluded in files.exclude and search.exclude (the exact same things fwiw, which seems redundant) and Quick Open is reasonable at least.

[jrieken]

Yeah, in jsconfig you cannot use glob patterns but you can spell out the full relative path to exclude things. Tho, by default the language brain only loads js and d.ts files. If with that you hit a limit there is only the option of multiple jsonfig files in subdirectories left...

[elsigh]

Ok, then it sounds like I don't need to exclude image directories anyway (but that accounts for some of the 10MB I mentioned earlier). It does seem that once I dismiss this warning it shouldn't continue to come back to bother me.

[jrieken]

Well, the problem is that language service is really struggling with large amount of files. Can you run wc -l 'find . -iname "*.js"' (' is actually a back tick) in a terminal to see with how many lines of JS code we are dealing? Or, iff possible, can you share the project with me?

[elsigh]

I can't share the code with you, but here's the result for that directory:
29264 total

[jrieken]

That should be OK. Today the warning is generated when there are more then 500 files. Once we adopt a newer version of TypeScript the language service will tell us more precisely when it has to much to chew on