Overriding tsconfig.json path

[CSchulz]

What would you like?

At the moment the ts-node configuration searches the tsconfig.json at the cypress config file location.
This should be overridable.

Why is this needed?

We are using different tsconfig.json files for local development and running on ci machines.
It would be nice to have the possibility to override the tsconfig.json path during the startup of cypress.

Other

No response

[AtofStryker]

Hey @CSchulz . We usually recommend putting the tsconfig inside the cypress directory, though you might need to include type definitions in the root. Does this work for your use case?

[CSchulz]

It works for me, but it doesn't satisfy my need for a second tsconfig.json file.
At local development we are building everything from scratch even the shared cypress parts. On the CI we are trying to reuse every built artifact so we are loading the shared cypress parts from the registry.
For this case we are using different path mappings in the tsconfig.json files.

[AtofStryker]

I believe that makes sense. I am going to mark this as a feature request then. It might be good to have a small repository that shows the use case / need if possible.