Support ESM style import syntax with file extension

[felixxxxxs]

Is there an existing issue that is already proposing this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe it

When using nest g in an ESM project ("type": "module" in package.json), the generated import lines are incorrect because they are missing the file extension ".js" at the end.

Describe the solution you'd like

The Nest CLI should automatically determine if the current project is using ESM syntax, and if so, append the file extension ".js" to the generated import lines.

Teachability, documentation, adoption, migration strategy

No response

What is the motivation / use case for changing the behavior?

Currently, I have to manually add ".js" to the end of each generated import line, which is annoying. 🙂