I agree that config and tooling are the hardest part of getting Typescript working. Everybody is saying use a framework, but if your use case deviates from the

I agree that config and tooling are the hardest part of getting Typescript working. Everybody is saying use a framework, but if your use case deviates from the frameworks it can get pretty difficult. My use case that was very tricky to config was. - SSR rendering of react in an express app (both typescript). -Trying to get VSCode visual debugger to work for both the client and server code paths. - Getting the various test libraries to work correctly (I still can’t get the NYC code coverage library to work). - Mix of ESM, CommonJS, misconfigured npm packages that don’t expose their types correctly. I ultimately used Vite, and got things working 90% the way I wanted and called it good enough.