Allow to specify the tsconfig.json filename explicitly

currently VSCode uses the file with the exact name tsconfig.json in the folder as the project file for a typescript project,

i have a few other project files named differently for corresponding sub-projects inside the same folder, I wish there was a way to tell VSCode to use one of them rather then the default tsconfig.json

[davidmatas]

I would love to see this implemented. I have problems for tests files that I think I would resolve if I can specify a tsconfig file to vscode.

The problem is my configuration for tsconfig excludes test files:

...
"exclude": [
    "node_modules",
    "**/*.test.ts",
    "**/*.test.tsx",
    "**/*.test.js"
  ]

When I open one of these files in vscode, it can’t resolve absolute paths I specify in compilerOptions:

"compilerOptions": {
...
  "paths": {
      "*": ["app/*", "*"],
  }
}

So I get a lot of ugly warnings

At the moment the workaround I’m using is leave tsconfig file for vscode dev development, and use differents tsconfig files for dev and production builds

[Qythyx]

I have a slightly different scenario that causes me to want this feature. My folder structure is:

MainProject/ –config/ ----bs-config.json ----tsconfig.json ----tslint.json –src/ –build/

I’m trying to put all my config files in that config folder instead of polluting the root. This works except that VSCode won’t detect my tsconfig.json in there.