Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Custom middleware does not work with esbuild because emitDecoratorMetadata is not supported
See original GitHub issuehttps://github.com/lukeautry/tsoa/issues/961
According to this ticket, tsoa doesn’t rely on the emitDecoratorMetadata TS option. That seemed correct at the time of writing, but sadly appears to no longer be true: https://github.com/lukeautry/tsoa/blob/acdfeb4d398fa7416dd10e251029d9e109c216d3/packages/runtime/src/decorators/middlewares.ts#L41
Because esbuild doesn’t support emitDecoratorMetadata, it appears that custom middleware via the @Middlewares annotation cannot be used with esbuild.
Is there any advice for a workaround?
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
Expected Behavior
Current Behavior
Possible Solution
Steps to Reproduce
Context (Environment)
Version of the library: Version of NodeJS:
- Confirm you were using yarn not npm: [ ]
Detailed Description
Breaking change?
Issue Analytics
- State:
- Created a year ago
- Comments:7
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
We fixed it. It turns out the issue is
import {Middlewares} from 'tsoa'. It works if we doimport {Middlewares} from '@tsoa/runtime'. This is surprising but it works. I guess I was barking up the totally wrong tree. Sorry about that and thanks for looking!@jsamilow thanks for the suggestion! Build fails if I’m importing from
tsoabut it works just fine with@tsoa/runtime