Skip to content
This repository was archived by the owner on Oct 16, 2020. It is now read-only.

Not reading configs from tsconfig.json #618

Open
ZSaberLv0 opened this issue Jul 9, 2019 · 1 comment
Open

Not reading configs from tsconfig.json #618

ZSaberLv0 opened this issue Jul 9, 2019 · 1 comment

Comments

@ZSaberLv0
Copy link

I'm using coc.nvim with javascript-typescript-stdio, but it seems not reading configs from my tsconfig.json

this. would trigger semantic completion correctly, but symbols from libs (or other dirs configured by tsconfig.json) can not be resolved

  • my LSP config should be correct, since this. would trigger semantic completion correctly
  • my project config should also be correct, since same config works for coc.nvim + typescript-language-server
  • tested these combination with similar results:
    • deoplete + vim-lsp
    • ncm2 + vim-lsp

here is my config for coc.nvim:

call coc#config('languageserver.typescript', {
        \   'command': &shell,
        \   'args': [&shellcmdflag, 'javascript-typescript-stdio'],
        \   'filetypes': ['typescript', 'javascript'],
        \ })

and for vim-lsp:

call lsp#register_server({
        \   'name' : 'typescript',
        \   'cmd' : [&shell, &shellcmdflag, 'javascript-typescript-stdio'],
        \   'whitelist' : ['typescript', 'javascript'],
        \ })

and the tsconfig.json:

{
    "compilerOptions": {
        "target": "es5",
        "outDir": "bin-debug",
        "experimentalDecorators": true,
        "lib": [
            "es5",
            "dom",
            "es2015.promise"
        ],
        "types": []
    },
    "include": [
        "src",
        "libs"
    ]
}
@tsujp
Copy link

tsujp commented Sep 17, 2019

+1 any news on this?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants