Closed uptownhr closed 2 months ago
I wonder if this is related to https://github.com/denoland/deno/issues/19160#issuecomment-1949548670
Hi @uptownhr thanks for reporting with very clear and concise code repository. We are looking into it, but as you guessed this looks related to decorator processing in Deno Deploy. We will get back to you once we figure out something.
@uptownhr We've identified the root cause. NestJS requires emitDecoratorMetadata
to be enabled in the compiler options, which Deno CLI handles correctly but Deno Deploy doesn't. We've fixed this issue in Deno Deploy and this will be shipping within the next few days.
Problem description
Here is the repo that is resulting in a different behavior when I run locally vs when ran in deno cloud.
My Github Project: Zap
Steps to reproduce
Local STR
Deno Cloud
Expected behavior
Expected Behavior: empty array Actual Behavior: I see a 500 error in the Deno Cloud Runtime. Error log from Deno Cloud below.
Environment
Version: Deno 1.44.0 OS: OSX
Possible solution
No response
Additional context
Logs from Deno Cloud deployment of error