how to specify custom tsconfig file?

[psulek]

I have tsconfig.json for build compatible with tsc 5.

And for linting im trying to use latest tsc v7 rc1 with oxlint and tsgolint, for this i created new tsconfig.tsgo.json with upgraded config (because some config like baseUrl does not exist in tsc7.

But i cant find a way to pass path to custom tsconfig file.

Is is possible now or not?

[krotname]

For the supported oxlint --type-aware path: no, not currently.

oxlint --tsconfig exists, but the CLI docs say it is for import resolution and that type-aware linting does not respect that option. It still discovers the relevant tsconfig.json for each file automatically.

That matches the current tsgolint headless code: cmd/tsgolint/headless.go creates a TsConfigResolver and calls FindTsConfigParallel(...) for the files. The headless payload has configs[].file_paths and configs[].rules, but no field for a custom tsconfig path.

There is a direct tsgolint --tsconfig PATH flag in cmd/tsgolint/main.go, but that path prints:

Warning: the `tsgolint` CLI entrypoint is unsupported!
Use Oxlint type-aware linting instead

So the practical workaround today is to make the lint/TSGo config discoverable as a normal tsconfig.json for the files being linted, or have the discovered tsconfig.json extend your tsconfig.tsgo.json. I would not rely on oxlint --tsconfig tsconfig.tsgo.json for type-aware linting, because the docs and current headless implementation point the other way.

[psulek]

Your proposed solution is not standard in ts ecosystem. For example tsx (https://tsx.hirok.io/typescript#custom-tsconfig-json-path) has --tsconfig for custom config, without it using default tsconfig.json file.

[krotname]

You're right. My workaround is not the standard TypeScript ecosystem UX; I should have framed it as "what works with the current supported oxlint type-aware path", not as a good long-term interface.

A --tsconfig / custom config path for type-aware linting would be the normal expectation. The reason I didn't suggest it as available is that current oxlint docs say its --tsconfig is for import resolution and type-aware linting still discovers tsconfig files automatically; the current tsgolint headless payload also does not appear to have a custom tsconfig field.

So I agree this is a valid feature request / UX gap. Extending the supported oxlint type-aware path to accept an explicit tsconfig would be cleaner than relying on tsconfig.json discovery or "make the default config extend the special one".