Micael Levi L. Cavalcante
Micael Levi L. Cavalcante
I didn't manage to change that without introducing a breaking changing at type level my attempt ```ts type AnArray = Array | ReadonlyArray; /** * Interface defining the property object...
it's working now ![image](https://user-images.githubusercontent.com/13461315/153772037-95209a6d-33aa-4722-8036-c1e184bf2d7a.png)
@43081j you could add the following badge in the README as well ``` [![npm bundle size](https://img.shields.io/bundlephobia/minzip/hanbi.svg)](https://www.npmjs.com/package/hanbi) ``` [![npm bundle size](https://img.shields.io/bundlephobia/minzip/hanbi.svg)](https://www.npmjs.com/package/hanbi) :sparkles:
@AlexRMU can you please share a code snippet?
indeed that was missed since v5 https://docs.nestjs.com/v4/components
here, `npm i cpu-features` breaks on Nodejs as well with the same error but `npm i ssh2` went fine while `bun i ssh2` doesn't and `ssh2` uses `buildcheck` on 'install'
@AaronTrazona so please close this issue
binded arguments in the "path" between function's decorator and parameters' decorators are different
I don't see anything wrong with that code snippet
binded arguments in the "path" between function's decorator and parameters' decorators are different
> In the object type case, how `@nestjs/swagger` composes the parameters (`OpenApiOperation.parameters`) ? type defs like that has not effect for `@nestjs/swagger` (the CLI plugin)
binded arguments in the "path" between function's decorator and parameters' decorators are different
it will work if you don't use types but concrete classes (with no decorators, if you're using the `@nestjs/swagger` plugin), due to how tsc works or if you use `@ApiParam()`,...