Closed
Description
From @ChiefORZ on May 30, 2017 11:28
- VSCode Version: Code 1.12.2 (19222cdc84ce72202478ba1cec5cb557b71163de, 2017-05-10T13:20:36.315Z)
- OS Version: Windows_NT ia32 6.1.7601
- Extensions:
Extension | Author | Version |
---|---|---|
project-manager | alefragnani | 0.18.0 |
one-monokai | azemoh | 0.2.4 |
npm-intellisense | christian-kohler | 1.3.0 |
path-intellisense | christian-kohler | 1.4.2 |
erb | CraigMaslowski | 0.0.1 |
vscode-eslint | dbaeumer | 1.2.11 |
githistory | donjayamanne | 0.2.0 |
gitlens | eamodio | 3.5.1 |
EditorConfig | EditorConfig | 0.9.3 |
prettier-vscode | esbenp | 0.17.1 |
vscode-console-wrapper | fabiodam | 0.4.0 |
php-debug | felixfbecker | 1.10.0 |
sublime-babel-vscode | joshpeng | 0.2.5 |
atom-keybindings | ms-vscode | 2.0.1 |
sort-imports | peterjuras | 2.3.1 |
better-merge | pprice | 0.7.0 |
code-settings-sync | Shan | 2.8.1 |
gitflow | vector-of-bool | 1.1.0 |
vscode-react-native | vsmobile | 0.3.2 |
JavaScriptSnippets | xabikos | 1.4.0 |
ReactSnippets | xabikos | 1.3.0 |
Material-theme | zhuangtongfa | 2.8.1 |
Resolving modules and Intellisense Autocompletion in our Project takes a long time...
Maybe this problem is a result of using absolute paths.
Here is our jsconfig.json
of the project:
{
"compilerOptions": {
"target": "es6",
"module": "es6",
"baseUrl": "./", // all paths are relative to the baseUrl
"paths": {
"~/*" : ["*"] // resolve any `~/foo/bar` to `<baseUrl>/foo/bar`
}
},
"exclude": [
"api",
"build",
"node_modules",
"public",
"seeds",
"sql_updates",
"tests.build"
]
}
Can i somehow debug which directories VSCode is resolving to find my correct file.
And is there maybe a way to cache this resolved pathy specific for this IDE on my Client... to make the IDE not search my Filesystem every time - or do you plan on make this in the future
Copied from original issue: microsoft/vscode#27539