relative import path (modulePath) should contain .js extension

[christophe-g]

Ideally relative Import path should contain the .js extension in the auto-generated routes.js file.

This would avoid an [ERR_MODULE_NOT_FOUND] errors in context not allowing extensionless module reference.

Sorting

• I'm submitting a ...

  • bug report
  • feature request
  • support request

• I confirm that I

  • used the search to make sure that a similar issue hasn't already been submit

Current Behavior

Generated code fail to run in some restricted context.

Expected Behavior

Auto-generated routes.js is always able to load imported modules

Possible Solution

• Run a post generation script to add missing .js extension. For instance, https://www.npmjs.com/package/fix-tsc-es-imports.

• Add .js in import { {{name}} } from '{{modulePath}}.js'; templates -

I can propose a PR i that make sense

[github-actions]

Hello there christophe-g 👋

Thank you for opening your very first issue in this project.

We will try to get back to you as soon as we can.👀

[mhammerc]

Hello,

By reading the configuration file documentation: https://github.com/lukeautry/tsoa/blob/master/packages/runtime/src/config.ts

I found that you can set

// tsoa.json
"routes": {
  "esm": true
}

The .js will be added automatically in the routes.ts file.

[christophe-g]

Oh - merci beaucoup @mhammerc !

Don't know how I missed that.

Closing as resolved