Roman
Here's a clean repro inside a Docker container: ```sh docker run --rm node:20.7.0 sh -c 'cd ~ && npx --yes projen new --from @10mi2/tms-projen-projects tms-apollo-graphql-app --sample-type=pothos-prisma' ```
Just tried it in Node `20.11.1`, which is the current latest LTS version and it results in the same error.
I think if we really want to add ESM support to projen, we need to do the following: 1. Create a battery of tests (matrix of Node versions, and CJS/ESM/both)...
> Please try again. To ensure you get the corrected version: Yes, that works! However, the project does use `.js` imports: ```ts import { decodeUserID } from "./users.js"; ``` Which...
> > Then we create an ESM version of these tests, which will, of course, all fail. But then we'll try to make it work. > > I don't think...
> That's _way_ outside the scope of this conversation, In general, I agree in terms of "opinion" - it is outside the scope of this. But it might not be...
> A yes, I avoid using it that way in general. There are _some_ cases I found this unavoidable. For example, using with `plop`: ```sh NODE_OPTIONS="--import tsx --no-warnings" plop ......
I am not a fan of abstracting away tsconfig to a third-party. Projen _is_ the config manager. By moving away the responsibility of the config upstream, then each projen-based project...
Would potentially make it opinionated then
What's blocking the release of this? I want to get started with this construct library, but don't want to deal with fixing breaking changes later, and after #346 (thanks, 🎉)...