[Feature] Allow to provide tsconfig path

Now there is no option that would allow you to specify which tsconfig to use when running playwright tests, I would like to have this option since my project uses several tsconfig’s

npx playwright test --tsconfig mega.tsconfig.json

[bellindj]

We have this issue. We’re using an NX monorepo. What we have is a setup like this:

libs/lib1/tsconfig.json libs/lib1/tsconfig.lib.json – overrides config for the library when built libs/lib1/tsconfig.spec.json – overrides config for test files libs/lib1/playwright.config.ts

libs/lib2/tsconfig.json libs/lib2/tsconfig.lib.json – overrides config for the library when built libs/lib2/tsconfig.spec.json – overrides config for test files libs/lib2/playwright.config.ts

Right now, we can’t use our tsconfig.spec.json files for playwright because it is always grabbing the tsconfig.json next to it. This is also why we ended up having a separate playwright config per lib (so that we could use our separate tsconfig.json files per project).

Ideally, we could pass in tsconfig.spec.json when we run playwright.

[JonWallsten]

@pavelfeldman This is really helpful in case you need different TS-settings for your build, test and working environment. We have one TS-config for VSCode/IntelliJ, one for the build process and one for testing. For VSCode we might want to include all files in the project for TS to pick up new files. In the build process we only want to use entry points. For testing we want less strict typing rules to avoid issues with third party tools etc.

This is our app right now:

So this would be really neat.