Custom tsconfig path

[Akany]

Is it possible to set plugin path to tsconfig ?

[DanielRosenwasser]

Whoops, misread the issue - what exactly do you mean?

[Akany]

Im using angular cli app. It adds tsconfig in src folder - not in root. Plugin doesnt see tsconfig.

[mhegazy]

@alexeagle is there a configuration to that can help move the tsconfig.json higher?

[alexeagle]

No, I believe the layout is fixed. But why is the plugin only looking in the root dir? Many projects keep their tsconfig.json under a src directory. I think this is a good idea, then you have a separate test/tsconfig.json since settings and deps are often different. cc @hansl

[hansl]

Agreed with Alex. There are many reasons why having multiple tsconfig spread through a project is a good idea.

[jednano]

In my case, I desire a separate tsconfig.json file for my npm prepublish command, which would allow me to transpile source files only (not test files) into a ./dist dir with definitions, but not sourcemaps.

[FourwingsY]

Is this issue still not yet solved?

[KubaJastrz]

https://github.com/Microsoft/TypeScript-Sublime-Plugin/blob/26bb7c57a31fc1b62bfc50e8ec652f7ef3f49ff1/typescript/commands/build.py#L22 passes project directory as a -p argument to tsc command, so it looks only for default tsconfig.json filename. Would be very helpful to allow different file, or even have different configs per folder in project.

[rgant]

This is an issue for me in my Angular project because while I want to allow es6 in my test spec files I don't want that in my actual app. Angular supports this natively by having one tsconfig file for spec and another for the app. Would be nice if I could configure this plugin to support that.

[maciej-zuk]

Any updates on this one?

[dandee]

I've got the same issue.

[kraktus]

bump, same with Sublime 4

[jpike88]

Wow I wish I saw this issue before messing around. This makes TS development untenable aside from the most basic of scenarios.