Open JavaScriptBach opened 2 months ago
Hello there JavaScriptBach 👋
Thank you for opening your very first issue in this project.
We will try to get back to you as soon as we can.👀
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days
Bump
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days
Bump
Sorting
I'm submitting a ...
I confirm that I
Expected Behavior
I work in a Typescript mono-repo, where all our imports are bare imports instead of relative imports. We define
exports
andimports
in package.json to control what each package exports. It would be great if tsoa knew how to resolve these imports.See https://github.com/JavaScriptBach/tsoa-repro for an example.
Current Behavior
tsoa does not know how to resolve these imports:
Steps to Reproduce
https://github.com/JavaScriptBach/tsoa-repro
Context (Environment)
Version of the library: 6.4.0 Version of NodeJS: 18.14.0
Detailed Description
It would be nice if tsoa understand how to resolve these fields:
These fields have been around since ~Node 12 and all major tooling (e.g. Typescript, bundlers) know how to understand them.
Currently, I can hack around this issue by passing custom tsconfig options to tsoa. But this is not ideal because I have to define the import paths in 2 different locations (package.json and in tsoa).
Breaking change?
This could break generation depending on what users have defined in their
exports
orimports
in package.json.