Micael Levi L. Cavalcante

Results 443 comments of Micael Levi L. Cavalcante

I don't think we need to switch to that one since AFIAK the whole point of adopting Express by default is due to its big ecosystem, not for performance reasons....

@dalidaliW Maybe we could have a new recipe page to showcase a "faster version of ExpressJS v4". If you'd like to have this, please open a new issue on the...

> I am not sure why this is the case 🤔 that may be related with having multiple `keyv` packages loaded in your app. Check that out! With NPM it...

As this is not supposed to be a package manager related issue, can you please update the reproduction to use NPM instead? then make sure that the commands are working...

I'm getting this SWC error on `npm run start:dev` ![Image](https://github.com/user-attachments/assets/75d715eb-69d1-4d70-b45c-0042b11e4561) ``` [Nest] 236146 - 05/09/2025, 4:10:11 PM ERROR [ExceptionHandler] TypeError: Cannot read properties of undefined (reading 'includes') at /tmp/nestjs-cache-manager/node_modules/keyv/dist/index.cjs:437:123 at...

I've managed to reproduce that using the code snippet from the nestjs docs. It only breaks if we use SWC builder but I'm not sure if this is something that...

![image](https://github.com/nestjs/nest/assets/13461315/15a87880-8bf4-4306-b2ab-d6104417934d) somehow it is loosing that reference [repro](https://stackblitz.com/edit/nestjs-typescript-starter-dnim2i?file=src%2Flazy%2Fone.service.ts) I tested with nestjs v9 as well.

this seems to be a bug with `lazyModuleLoader#load` when the module is resolved already (cached) because it works as expected when `lazyModuleLoader#load` returns a new instance every time

can't we achieve this already with https://docs.nestjs.com/techniques/logger#extend-built-in-logger ?

If I'm not wrong, that `ConsoleLogger` is public (ie., can be used by other devs to change logger formatting etc as per https://docs.nestjs.com/techniques/logger#extend-built-in-logger). And so adding a new mandatory method...