Jackie McDoniel
Jackie McDoniel
Bun now supports `emitDecoratorMetadata` as of `1.0.3`. I've tested this with the following: ``` nest new bun-test --skip-install -p npm cd bun-test bun install bun run src/main.ts ``` It now...
Didn't check for memory consumption, was more concerned if it worked in the first place
@vnenkpet Bun as a package manager does indeed work with Nest. Bun as a runtime _mostly_ works, but there are still quirks with pino and fastify, [as I've already mentioned](https://github.com/nestjs/nest-cli/pull/2223#issuecomment-1731739879)....
Renovate's `Dependency Dashboard` issue (this) is a rolling issue that constantly gets updated with links to open PRs by the Renovate bot to show what is currently available for update...
> The current evaluation order is illogical. `process.env` shouldn't take precedent over custom configuration files. If we ignore `process.env` then that would mean approaches like `PORT=8080 nest startt --watch` would...
Seems like some sort of issue with usd adding `this.once('drain')` [here](https://github.com/nestjs/nest/blob/master/packages/core/router/sse-stream.ts#L119). Interestingly it doesn't happen when using rxjs directly via `interval` Stack Trace ``` (node:1588817) MaxListenersExceededWarning: Possible EventEmitter memory leak...
The thing is, it _can_ accept `Readable` as you mentioned, with the right configuration. While it may be a better solution, in terms of memory management, it's also a more...
Perhaps we can make a mention in the docs and the default of buffer and how to use streams if that is the desired approach and why you might want...
Should we also add the `metadata.type` so if there are multiple `foo` fields the user knows which one specifically caused the error (body, query, param, custom)?
No. There's still a type issue that I'm trying to work back out