Clarify emitDecoratorMetadata requirement in getting-started #78
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follows #77
Fully addresses lukeautry/tsoa#1443
Why consider this change?
emitDecoratorMetadata
has significant consequences for output JSimport
vsimport type
, etc) are no longer build-only risks. They can now impact runtime code when you have this setting enabledemitDecoratorMetadata
is particularly troublesome withisolatedModules
, which is required by projects like esbuild, vite, swc, babel, next.js, and create-react-appemitDecoratorMetadata
is required or not