Vetur Intellisense slow and incomplete if project has jsconfig #547

Akryum · 2017-11-15T14:48:17Z

I have searched through existing issues
I have read through docs
I have read FAQ

Info

Platform: Win
Vetur version: 0.11.3
VS Code version: 1.18.0

Problem

Vetur shows incomplete Intellisense and it takes too much time.
It works fine if the project is virtual (no jsconfig or tsconfig).

Reproducible Case

https://github.com/Akryum/devfest-nantes-2017/tree/vs-code/app

Open this folder in VS Code and try Vetur in a .vue file.

The text was updated successfully, but these errors were encountered:

HerringtonDarkholme · 2017-11-16T06:47:57Z

I cannot reproduce this. Though at first load, I can feel some delay.

This is caused by automatic typing resolution in vscode: vscode will automatically install typing file used in your project. After initial loading, I cannot feel significant delay.

Akryum · 2017-11-16T07:22:20Z

How long does this take for you ? Le jeu. 16 nov. 2017 à 07:48, Herrington Darkholme <notifications@github.com> a écrit :

…

I cannot reproduce this. Though at first load, I can feel some delay. This is caused by automatic typing resolution in vscode: vscode will automatically install typing file used in your project. After initial loading, I cannot feel significant delay. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#547 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACqyfMjv5F0M7matNLlxpthVDP4N12Bbks5s29qegaJpZM4QfChO> .

HerringtonDarkholme · 2017-11-16T08:03:50Z

About 3 seconds.

Akryum · 2017-11-16T08:06:15Z

And do you have complete Intellisense with props, computed, methods, and Vue API inside the component?

Akryum · 2017-11-16T08:07:01Z

Did you try on Windows 10?

HerringtonDarkholme · 2017-11-16T08:08:01Z

Nope, I'm on MBP. @octref do you have windows box ?

Akryum · 2017-11-16T08:16:21Z

I tested on a MBP, I cannot reproduce the slowness, but I can reproduce the incompleteness. For example, in the PageHome.vue component:

Inside the emptyMessage computed prop, I should have questions, loading, refresh and all the other Vue API (like $refs) also suggested, but I only have emptyMessage.
Inside the refresh method, I only have refresh suggested.

octref · 2017-11-16T15:50:39Z

I do have a Windows machine at home. I can try it later today.

I'll take a look at the incomplete IntelliSense.

TristinDavis · 2017-12-08T16:39:34Z

Any update on the incomplete IntelliSense issue?

Hanruis · 2017-12-22T07:43:12Z

I have the same problem , any update on this issue ?

HerringtonDarkholme · 2018-01-16T15:54:43Z

Can you try intelisense in JS file or TS file?

Vetur shares the same TypeScript engine with VSCode. So the problem should also occur there.

doommm · 2018-01-23T13:00:23Z

Have same issue.
Intelisense works slow in .vue file, and works fine in .ts.
So for a better coding performance, i have to separate SFC into .vue and .ts.

VSCode 1.19.2, Win10 1703 x64
Vetur 0.11.6
TypeScript 2.6.2

The config include in tsconfig is setted as below. There are almost 300 files in these directories(.vue, .js, .ts).

// tsconfig.json
    "include": [
        "./Scripts/**/*",
        "./components/**/*",
        "./src/**/*"
    ],

HerringtonDarkholme · 2018-01-23T13:04:21Z

Please do provide a reproduction repo if you have the same issue.

Akryum · 2018-01-29T10:20:42Z

@octref Did you have time to check the reproduction on Windows to see if you have the issue?

octref · 2018-01-31T17:26:37Z

@Akryum I tested on a Windows VM running in Parallel. I do feel some lagginess in the beginning, but after a while the completion becomes smooth. What's your machine's spec?

Meanwhile I tested the project on both macOS / Win, interestingly, the incomplete completion only happens on Windows...Looking into it.

Akryum · 2018-01-31T17:32:20Z

Windows 10 Pro 64-bit
Intel i7 3770K @ 4GHz (4 cores/8 threads)
16 GB DDR3

RenanOliv · 2018-02-02T17:46:18Z

@octref I was able to reproduce this issue with a couple files in this repository. I managed to find two cases that neither intellisense or path suggestions works. I hope this information can help somehow.

Specs that I used to reproduce the issue

Windows 10 Version 1709
Visual Studio Code Update 1.19.3
Vetur Version 0.11.7

Open folder has a subfolder with a `jsconfig.json` file

sample-vetur-jsconfig\sub-folder-example

Intellisense: works on .js files only
Path suggestions: works on .js files only

Open folder has a root `jsconfig.json` file

sample-vetur-jsconfig\sub-folder-example\js

Intellisense: works on .js and .vue files
Path suggestions: works on .js and .vue files

Open folder has a root `jsconfig.json` file with path aliases

sample-vetur-jsconfig\root-folder-example

Intellisense: works on .js and .vue files
Path suggestions: works on .js and .vue files. But not with alias (.js and .vue).

I've looked further in this case and I saw this issue in the TypeScript repository that mentions this behaviour.
I believe this issue may also affect vetur suggestions. But I'm not sure if this fix is available in the stable release or not. 🤔

There is also a fourth case that vetur is not understanding the baseUrl value in root jsconfig.json if your value is a subfolder like "baseUrl": "./js",. In this last one both Intellisense and path suggestion will work on .js files but not on .vue files.

Hanruis · 2018-04-24T13:40:13Z

updated 2018-5-8
after more debug, I found that remove the ./src/* in include of jsconfig.json, can fix this problem.

=======================================

for the slow problem, I try to run simple profile.

after profiling by devtool, I found that large project with jsconfig.json or tsconfig.json cause this host.getScriptFilaNames returns a large array of filePath, and this will cause ts language service run
HostCache.createEntry huge times。

the host.getScriptFileNames returns

the profile

wasichris · 2018-05-02T16:59:55Z

same intellisense slow issue with jsconfig.json

zcoding · 2018-05-24T09:12:07Z

same intellisense slow issue

delay about 3 seconds...

octref · 2018-05-24T20:15:05Z

Can you try this thing now:

Edit setting "vetur.trace.server": "verbose"
Go to Output -> Vue Language Server
Trigger completion
Paste result here

uriannrima · 2018-06-10T03:31:21Z

Having the same trouble, as I write intellisence takes a couple of seconds (about 3) to say something (error, autocomplete, etc), and as I'm writing, it starts to give the intellisence response from the previous text. So it seems to send at each key that I press, instead of maybe wait for me to stop writing or something.

I've enabled the verbose output, it printed like a LOT of text, how should I share here? I mean, it's really a LOT to paste in here.

Hanruis · 2018-06-11T01:50:30Z

@uriannrima if more than hundreds line of the output, provide a file for download would be better, i think.

octref · 2018-08-12T21:40:53Z

@Akryum Does this still happen to you?
@uriannrima You can paste log files up to 10MB to GitHub.

UltimaBeaR · 2018-09-29T06:07:09Z

Had same issue. Regular .js files were fine, but not .vue files. Fixed it by adding "include" in jsconfig.json:

{
  "include": [
    "./src/**/*"
  ],
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "~/*": ["src/*"],
      "src/*": ["src/*"],
      "vendor-dll/*": ["vendor-dll/*"]
    },
    "reactNamespace": "h"
  }
}

tartinesKiller · 2018-09-29T16:10:17Z

I experience the same behaviour, but I've noticed something strange: I've got two projects with the same jsconfig.json, quite the same folder structure, but intellisense is very slow on one, and fast as hell on the other.
Here is the jsconfig:

{
    "compilerOptions": {
        "baseUrl": ".",
        "module": "es6",
        "paths": {
            "@/*": ["*", "./src/*"],
            "@static/*": ["*", "./static/*"],
        },
        "moduleResolution": "node"
    },
    "include": [
        "./src/**/*"
    ],
}

I've noticed in the Vetur logs that the task "textDocument/completion" took 158ms for the "fast" project, and 4904ms for the "slow" project. Both are quite small projects, but I can't share them, sorry.
May it help if I share the vetur logs?

tartinesKiller · 2018-09-30T16:08:55Z

Changing moduleResolution in compilerOptions from node to classic on the slow project seems to fix the slowness, even if I don't understand why it runs without problem like that on the fast project. If that can help anyone.

octref · 2018-10-01T15:20:25Z

Changing moduleResolution in compilerOptions from node to classic on the slow project seems to fix the slowness

@tartinesKiller That's because we are using the TypeScript language service that turns on/off features based on the tsconfig.json file. I'll try to repro this.

octref · 2018-10-01T23:53:36Z

@tartinesKiller Changing the module resolution to node does not repro it for me in this project: https://github.com/octref/veturpack

Can you also try another build? See #913 (comment). Thanks in advance.

momocow · 2018-10-02T04:08:51Z

Same slowness here on my notebook. (about 3 secs)

Both path suggestion and intellisense work but are slow.
(paths alias in jsconfig.json also works.)

System info

Win10 Home (10.0.17134)
i7-7700HQ

Specs

Vue.js Extension Pack 1.1.3
Vetur 0.12.7
VSC 1.27.2

Here's my jsconfig.json.

{
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "@/*": [ "./src/*" ]
    }
  }
}

After I rename it to jsconfig2.json (the same effect as removing it from the project), the slowness is fixed.
Adding or removing include has no effect to fix the slowness.
(After each change, VSC was restarted)

But with the same jsconfig.json, I cannot reproduce the slowness in a minimal project yet.
(I should look into what the differences are between the minimal project and my current one)

octref · 2018-10-02T16:28:21Z

@momocow Thanks a lot for the info! If you remove paths, is the slowness gone?

momocow · 2018-10-03T10:29:46Z

No, almost the same.
Only removing jsconfig.json eliminates the slowness.

Hanruis · 2018-10-08T01:57:57Z

@momocow how about just remove the ./src/* of include .

I have found that it will make vetur anylasis all files in the src dir. And the slowness occur while src dir has large amount js and vetur files. In my project, there are more than 1000 files in src dir.

momocow · 2018-10-08T04:18:28Z

@Hanruis My project is not that big, containing 10 .vues and 4 .jss only.

BTW, a good news is that after auto-updating vetur from v0.12.7 to v0.13.0, the slowness is gone even with the jsconfig.json as follows. 😂
I cannot reproduce the slowness yet.

{
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "@/*": [ "./src/*" ]
    }
  },
  "include": [
    "src"
  ]
}

david-mart · 2018-12-14T01:30:22Z

Setting "moduleResolution": "classic" in compilerOptions seems to fix the slowness. However, it disables node_modules intellisense on some modules.

zbjornson · 2018-12-23T03:51:53Z

@octref here's a somewhat abbreviated output from the verbose log (I removed some of the response bodies, or parts of large response bodies). You can see the responses often take 2-3+ seconds. The responses from the typescript server on the same computer take 75 to 250 ms generally.

[Trace - 7:15:48 PM] Sending notification 'textDocument/didChange'.
Params: {
    "textDocument": {
        "uri": "file:///c%3A/Users/zachb/git/repo/public/src/components/Tag.vue",
        "version": 37
    },
    "contentChanges": [
        {
            "text": <5,295 characters>
        }
    ]
}

[Trace - 7:15:48 PM] Sending request 'textDocument/completion - (96)'.
Params: {
    "textDocument": {
        "uri": "file:///c%3A/Users/zachb/git/repo/public/src/components/Tag.vue"
    },
    "position": {
        "line": 107,
        "character": 4
    },
    "context": {
        "triggerKind": 1
    }
}

[Trace - 7:15:48 PM] Sending notification '$/cancelRequest'.
Params: {
    "id": 96
}

[Trace - 7:15:48 PM] Sending notification 'textDocument/didChange'.
Params: {
    "textDocument": {
        "uri": "file:///c%3A/Users/zachb/git/repo/public/src/components/Tag.vue",
        "version": 41
    },
    "contentChanges": [
        {
            "text": <5,321 characters>
        }
    ]
}

[Trace - 7:15:48 PM] Sending request 'textDocument/completion - (97)'.
Params: {
    "textDocument": {
        "uri": "file:///c%3A/Users/zachb/git/repo/public/src/components/Tag.vue"
    },
    "position": {
        "line": 107,
        "character": 8
    },
    "context": {
        "triggerKind": 2,
        "triggerCharacter": "."
    }
}

[Trace - 7:15:49 PM] Received response 'textDocument/completion - (96)' in 712ms.
Result: {
    "isIncomplete": false,
    "items": [
        {
            "uri": "file:///c%3A/Users/zachb/git/repo/public/src/components/Tag.vue",
            "position": {
                "line": 107,
                "character": 4
            },
            "label": "arguments",
            "sortText": "00",
            "kind": 6,
            "data": {
                "languageId": "javascript",
                "uri": "file:///c%3A/Users/zachb/git/repo/public/src/components/Tag.vue",
                "offset": 2019
            }
		},
		// ... 2,523 items elided
        {
            "uri": "file:///c%3A/Users/zachb/git/repo/public/src/components/Tag.vue",
            "position": {
                "line": 107,
                "character": 4
            },
            "label": "of",
            "sortText": "02525",
            "kind": 14,
            "data": {
                "languageId": "javascript",
                "uri": "file:///c%3A/Users/zachb/git/repo/public/src/components/Tag.vue",
                "offset": 2019
            }
        }
    ]
}


[Trace - 7:15:49 PM] Sending request 'textDocument/documentSymbol - (98)'.
Params: {
    "textDocument": {
        "uri": "file:///c%3A/Users/zachb/git/repo/public/src/components/Tag.vue"
    }
}


[Trace - 7:15:49 PM] Sending request 'textDocument/documentLink - (99)'.
Params: {
    "textDocument": {
        "uri": "file:///c%3A/Users/zachb/git/repo/public/src/components/Tag.vue"
    }
}

[Trace - 7:15:49 PM] Sending request 'textDocument/documentColor - (100)'.
Params: {
    "textDocument": {
        "uri": "file:///c%3A/Users/zachb/git/repo/public/src/components/Tag.vue"
    }
}

[Trace - 7:15:49 PM] Received notification 'textDocument/publishDiagnostics'.
Params: {
    "uri": "file:///c%3A/Users/zachb/git/repo/public/src/components/Tag.vue",
    "diagnostics": [
        {
            "range": {
                "start": {
                    "line": 107,
                    "character": 3
                },
                "end": {
                    "line": 107,
                    "character": 4
                }
            },
            "severity": 1,
            "message": "Cannot find name 't'."
        }
    ]
}

[Trace - 7:15:50 PM] Received response 'textDocument/completion - (97)' in 1957ms.
Result: {
    "isIncomplete": false,
    "items": [
        {
            "uri": "file:///c%3A/Users/zachb/git/repo/public/src/components/Tag.vue",
            "position": {
                "line": 107,
                "character": 8
            },
            "label": "badgeClasses",
            "sortText": "00",
            "kind": 5,
            "data": {
                "languageId": "javascript",
                "uri": "file:///c%3A/Users/zachb/git/repo/public/src/components/Tag.vue",
                "offset": 2023
            }
        },
		// ... 149 items elided
        {
            "uri": "file:///c%3A/Users/zachb/git/repo/public/src/components/Tag.vue",
            "position": {
                "line": 107,
                "character": 8
            },
            "label": "contains",
            "sortText": "151",
            "kind": 17,
            "data": {
                "languageId": "javascript",
                "uri": "file:///c%3A/Users/zachb/git/repo/public/src/components/Tag.vue",
                "offset": 2023
            }
        }
    ]
}

[Trace - 7:15:50 PM] Sending request 'completionItem/resolve - (101)'.
Params: {
    "label": "badge",
    "insertTextFormat": 1,
    "kind": 5,
    "sortText": "05",
    "data": {
        "languageId": "javascript",
        "uri": "file:///c%3A/Users/zachb/git/repo/public/src/components/Tag.vue",
        "offset": 2023
    }
}

[Trace - 7:15:51 PM] Received notification 'textDocument/publishDiagnostics'.
Params: {
    "uri": "file:///c%3A/Users/zachb/git/repo/public/src/components/Tag.vue",
    "diagnostics": [
        {
            "range": {
                "start": {
                    "line": 107,
                    "character": 8
                },
                "end": {
                    "line": 107,
                    "character": 8
                }
            },
            "severity": 1,
            "message": "Identifier expected."
        }
    ]
}

[Trace - 7:15:51 PM] Received response 'textDocument/documentSymbol - (98)' in 2852ms.
Result: [
    {
        "name": "docs",
        "location": {
            "uri": "file:///c%3A/Users/zachb/git/repo/public/src/components/Tag.vue",
            "range": {
                "start": {
                    "line": 0,
                    "character": 0
                },
                "end": {
                    "line": 41,
                    "character": 7
                }
            }
        },
        "containerName": "",
        "kind": 8
    },
	// ... about 100 items elided
    {
        "name": ".pb-tag__badge + .pb-tag__dismiss",
        "kind": 5,
        "location": {
            "uri": "file:///c%3A/Users/zachb/git/repo/public/src/components/Tag.vue",
            "range": {
                "start": {
                    "line": 225,
                    "character": 0
                },
                "end": {
                    "line": 227,
                    "character": 1
                }
            }
        }
    }
]

[Trace - 7:15:51 PM] Received response 'textDocument/documentLink - (99)' in 2656ms.
// (removed)

[Trace - 7:15:52 PM] Received response 'textDocument/documentColor - (100)' in 3230ms.
// (removed)

[Trace - 7:15:52 PM] Received response 'completionItem/resolve - (101)' in 1840ms.
// (removed)

gambolputty · 2019-02-21T00:42:31Z

No Intellisene for me in Vue files, but in js files. After replacing the exclude with the include option in my jsconfig.json it worked (thanks @UltimaBeaR!):

{
  "compilerOptions": {
    "target": "es2017",
    "baseUrl": "src",
    "module": "commonjs"
  },
  "include": ["./src/**/*"]
}

karlito40 · 2019-02-26T22:13:27Z

I'm encountering the same problem with the emmet auto suggestion on all my SFC. In my case it looks to be cause by the size of my project. Everything works fine when i load those components in a separate vscode window.

Removing my .jsconfig does also make the auto suggestions appear.

coppyC · 2019-02-27T09:24:07Z

me too,
finally, I find it work slow with jsconfig.json.
It work bad on my old note computer with third generations i5 ,
and work very fastly on my new computer with i7 8700.
but in js (not vue ), all they work very fast.
I think Vetur has High cpu usage with jsconfig.json / tsconfig.json.
#913

mattixittam · 2019-03-11T14:22:26Z

Can confirm 2-second delay for suggestions on my 2017 MBP using jsconfig in my project (containing about 500 .vue/.js files).

The jsconfig file doesn't even need to contain anything. An empty jsconfig (or one containing an empty object) triggers the delay as well.

octref · 2019-05-08T00:21:09Z

This should be fixed in 0.20.0. A small summary:

Vetur used to read all files included in js/tsconfig.json
Besides that, Vetur would read their dependencies, even if they are in node_modules
This is triggered on each file update, auto completion etc, so it's very exepensive

New way it works:

All file system access to node_modules are cached and frozen (since they likely won't change).
Local vue/js/ts file access are cached. When they are updated, caches are purged.

qwqcode · 2019-12-22T08:30:12Z

This should be fixed in 0.20.0. A small summary:

Vetur used to read all files included in js/tsconfig.json

Besides that, Vetur would read their dependencies, even if they are in node_modules

This is triggered on each file update, auto completion etc, so it's very exepensive

New way it works:

All file system access to node_modules are cached and frozen (since they likely won't change).

Local vue/js/ts file access are cached. When they are updated, caches are purged.

But if node_modules are frozen, when i use npm link, it seems that autocomplete cannot refresh after I made some changes to the code.

in .vue file

In .ts file it is working

gooqiao · 2020-03-27T17:58:50Z

This should be fixed in 0.20.0. A small summary:

Vetur used to read all files included in js/tsconfig.json

Besides that, Vetur would read their dependencies, even if they are in node_modules

This is triggered on each file update, auto completion etc, so it's very exepensive

New way it works:

All file system access to node_modules are cached and frozen (since they likely won't change).

Local vue/js/ts file access are cached. When they are updated, caches are purged.

But if node_modules are frozen, when i use npm link, it seems that autocomplete cannot refresh after I made some changes to the code.

in .vue file

In .ts file it is working

I have this problem, too.
@octref

rennzhang · 2021-08-12T07:43:27Z

我在 vue2中没有这个问题，vue3中很严重，大概有2~3s 的延迟

gah98 · 2021-12-15T07:02:53Z

How to solve this problem

carlos00027 · 2022-02-04T23:16:01Z

in root folder create file vetur.config.js

module.exports = {
// optional default: {}
// override vscode settings
// Notice: It only affects the settings used by Vetur.
settings: {
"vetur.useWorkspaceDependencies": true,
"vetur.experimental.templateInterpolationService": true
},
}

Akryum changed the title ~~Vetur slow and incomplete if project has jsconfig~~ Vetur Intellisense slow and incomplete if project has jsconfig Nov 15, 2017

Akryum mentioned this issue Nov 15, 2017

autocomplete suggest appear too slow #378

Closed

octref added the bug label Jan 31, 2018

octref mentioned this issue Feb 13, 2018

High CPU Usage on macOS & dependency resolution failure #691

Closed

3 tasks

elevatebart mentioned this issue Aug 6, 2018

Enable F12 navigation in vscode bencodezen/vue-enterprise-boilerplate#72

Closed

octref added the perf label Aug 10, 2018

octref mentioned this issue Aug 13, 2018

Vetur 1.0 Roadmap #873

Open

17 tasks

octref mentioned this issue Nov 5, 2018

关于vscode 在vue文件中书写ts 代码感知提示慢的问题 #948

Closed

3 tasks

zbjornson mentioned this issue Jan 10, 2019

Server crash, resolved by upgrading typescript #1054

Closed

3 tasks

coppyC mentioned this issue Feb 28, 2019

[2019-02-28] vscode中开发vue的最佳实践 coppyC/blog#1

Closed

This was referenced Apr 3, 2019

Extension causes high cpu load #1179

Closed

Extension causes high cpu load #1126

Closed

octref closed this as completed May 8, 2019

Vetur Intellisense slow and incomplete if project has jsconfig #547

Vetur Intellisense slow and incomplete if project has jsconfig #547

Comments

Akryum commented Nov 15, 2017

Info

Problem

Reproducible Case

HerringtonDarkholme commented Nov 16, 2017

Akryum commented Nov 16, 2017 via email

HerringtonDarkholme commented Nov 16, 2017

Akryum commented Nov 16, 2017

Akryum commented Nov 16, 2017

HerringtonDarkholme commented Nov 16, 2017

Akryum commented Nov 16, 2017

octref commented Nov 16, 2017

TristinDavis commented Dec 8, 2017

Hanruis commented Dec 22, 2017

HerringtonDarkholme commented Jan 16, 2018

doommm commented Jan 23, 2018 • edited Loading

HerringtonDarkholme commented Jan 23, 2018

Akryum commented Jan 29, 2018

octref commented Jan 31, 2018

Akryum commented Jan 31, 2018

RenanOliv commented Feb 2, 2018 • edited Loading

Specs that I used to reproduce the issue

Open folder has a subfolder with a jsconfig.json file

Open folder has a root jsconfig.json file

Open folder has a root jsconfig.json file with path aliases

Hanruis commented Apr 24, 2018 • edited Loading

wasichris commented May 2, 2018

zcoding commented May 24, 2018

octref commented May 24, 2018 • edited Loading

uriannrima commented Jun 10, 2018

Hanruis commented Jun 11, 2018

octref commented Aug 12, 2018

UltimaBeaR commented Sep 29, 2018

tartinesKiller commented Sep 29, 2018

tartinesKiller commented Sep 30, 2018

octref commented Oct 1, 2018

octref commented Oct 1, 2018

momocow commented Oct 2, 2018 • edited Loading

octref commented Oct 2, 2018

momocow commented Oct 3, 2018

Hanruis commented Oct 8, 2018

momocow commented Oct 8, 2018 • edited Loading

david-mart commented Dec 14, 2018

zbjornson commented Dec 23, 2018

gambolputty commented Feb 21, 2019

karlito40 commented Feb 26, 2019 • edited Loading

coppyC commented Feb 27, 2019

mattixittam commented Mar 11, 2019 • edited Loading

octref commented May 8, 2019

qwqcode commented Dec 22, 2019 • edited Loading

gooqiao commented Mar 27, 2020 • edited Loading

rennzhang commented Aug 12, 2021

gah98 commented Dec 15, 2021

carlos00027 commented Feb 4, 2022 • edited Loading

doommm commented Jan 23, 2018 •

edited

Loading

RenanOliv commented Feb 2, 2018 •

edited

Loading

Open folder has a subfolder with a `jsconfig.json` file

Open folder has a root `jsconfig.json` file

Open folder has a root `jsconfig.json` file with path aliases

Hanruis commented Apr 24, 2018 •

edited

Loading

octref commented May 24, 2018 •

edited

Loading

momocow commented Oct 2, 2018 •

edited

Loading

momocow commented Oct 8, 2018 •

edited

Loading

karlito40 commented Feb 26, 2019 •

edited

Loading

mattixittam commented Mar 11, 2019 •

edited

Loading

qwqcode commented Dec 22, 2019 •

edited

Loading

gooqiao commented Mar 27, 2020 •

edited

Loading

carlos00027 commented Feb 4, 2022 •

edited

Loading