Closed whitestripe42 closed 2 years ago
Seems like this can be fixed by explicitly adding the dotted directory to tsconfig.json
's include
array, however, it isn't picked up if include
just contains a wild card like ./**/*
. Further, other tools consuming the same tsconfig.json
seem to pick the directory up with just the wildcard.
// tsconfig.json
// Works
include: [".something/**/*"]
// Import error in tsserver, but not in other tools
include: ["./**/*"]
https://github.com/microsoft/TypeScript/issues/13399
Okay, seems like this behaviour is correct, and the "other tools" (in this case, Webpack with Typescript config file) are probably transpiling their config files irrespective of the directory structure.
Describe the bug
Importing JSON from a directory outside of a dotted directory gives an error, even though
compilerOptions.resolveJsonModules
istrue
in mytsconfig.json
.Reproduce the bug
There is no error in
something/index.ts
, however, in.something/index.ts
I get an error:init.vim
coc-extensions
Result from CocInfo
Log of coc.nvim