Add .js extension to imports to support ES Modules
See: https://nodejs.org/api/esm.html#mandatory-file-extensions
Hey @ferdikoomen 👋 any objections to merging this? We're also depending on this PR. Thanks!
How are you consuming the output, inside a nodeJS application? Because the requirement to have .js inside imports is a Node specific issue, maybe we should limit these changes to the nodeJS client (or have it as a build flag?) Right now it throws all kinds of import warnings on older / bundled / browser based projects
any progress?
https://github.com/ferdikoomen/openapi-typescript-codegen/issues/1381
Is there something stopping this from being merged? Blocking our adoption atm
I'm very interested in this as well
so are we. we use this package to create an isomorphic api client and so being able to use node esm resolution would be nice.
What issue are you trying to solve here? I fail to see how this will solve anything, as it is just a PR (with no issue connected describing what the problem is). What we have is a link to an ESM page, as if that was enough, but this project is not an ESM project.
What we really want is a solution to this issue #1182 right?