Momo Kornher

Okay, so it seems like `ts-node --esm` is what's needed. This is the minimal change I did come up with: ``` const project = new typescript.TypeScriptProject({ // ... tsconfigDev: {...

Can you try and gather more feedback from the community on this RFC?

Ha you are right, apologies! I think I misread the ts-node docs. I can conform this works for me now: ```ts const project = new typescript.TypeScriptAppProject({ //... tsconfigDev: { compilerOptions:...

> I'm not sure I follow completely, but I'll take a swing at it: I was just saying that tsx works in my testing in both ESM (future) and non-ESM...

Oh no, I see the confusion now. Sorry for being unspecific. What I meant is: - You are proposing to extend the existing `typescript.Projenrc` component with a new option (e.g....

> On a slightly different note, how should I proceed? My eventual goal is to chip away at ESM support with several smaller Issue→PR steps. I have several projects that...

> I'm not sure how 'ProjenrcUsingTsx' would work. Or why, really. Nothing _in_ the `.projenrc.ts` file would change, and nothing in the output would change other than the command in...

> Having the GitHub pipeline run tests on multiple node versions would be great, and likely for other reasons than just ESM. That should be a straight forward PR. We...

6 months on, I'm warming up to `tsx`. Seems like it's getting broad adoption now and has wide feature support.

> > Having the GitHub pipeline run tests on multiple node versions would be great > > @mrgrain Would you consider that a requirement for this effort? I don't see...