feat: also generate a tsconfig.json when using TypeScript

[dcrousso]

fixes microsoft/playwright#41246

[Skn0tt]

Do we need the target/module/moduleResolution fields in the config? When I open it in VS Code, things work just fine without the fields, and only types added.

[Skn0tt]

With TypeScript 6, the default for types changed: https://devblogs.microsoft.com/typescript/announcing-typescript-6-0/#types-now-defaults-to-[]

This means we need to add "types": ["node"] here. It's weird that TypeScript docs on this aren't yet updated 🤔 microsoft/TypeScript#63392

[Skn0tt]

I get this compiler warning:

Option 'moduleResolution=node10' is deprecated and will stop functioning in TypeScript 7.0. Specify compilerOption '"ignoreDeprecations": "6.0"' to silence this error.
  Visit https://aka.ms/ts6 for migration information.ts

Node is an alias to node10. I think we should go with bundler, since TypeScript doesn't do any compilation in our case and Playwright has it's own loader with lax semantics around module resolution:

Suggested change

	"moduleResolution": "Node",
	"moduleResolution": "bundler",

[dcrousso]

Do we need the target/module/moduleResolution fields in the config? When I open it in VS Code, things work just fine without the fields, and only types added.

i was searching around trying to find a minimum viable tsconfig.json and those two fields were frequently listed (not to mention they're in our docs https://github.com/microsoft/playwright/blob/main/docs/src/test-typescript-js.md)

but if you dont think theyre necessary then i can remove :)

[Skn0tt]

The fields weren't necessary in my testing, and we haven't heard about it from Component Testing folks who already use this file. I'd ship without target, but leaving it up to you.