Add resilience and decorator libraries

[LeoVS09]

Pull Request

Type of Change

• Adding a new resource

Description

Adding two libraries:

• nestjs-resilient-client
• nestjs-decorators

Checklist

Please ensure your PR meets the following requirements:

• I have read the contribution guidelines
• The resource I'm adding has at least 10 GitHub stars (if applicable)
• The link I'm adding is working and points to the correct resource
• I have placed the resource in the appropriate category
• The description is clear and concise
• I have followed the existing format:
  • - [Name](URL) - Description.
  • For libraries with star badges: - ![](star-badge-url) [Name](URL) - Description.

Resource Details (if adding a new resource)

NestJS Resilient Client

• Name: nestjs-resilient-client
• URL: https://github.com/NeoLabHQ/nestjs-resilient-client
• Category: Reliability
• GitHub Stars (if applicable): 1
• Why is this resource valuable to the NestJS community?: In the TypeScript and NestJS ecosystem, there are multiple projects that provide different kinds of resilience utilities, but none cover all patterns as well as the famous Polly from the .NET ecosystem. On top of that, all of the existing solutions are pretty complex and hard to manage for new developers. This library provides a very pragmatic and zero-configuration resilience setup for the HTTP client that is suitable for the majority of workloads. It is backward-compatible with the default NestJS HttpService, so to make your service resilient, it is enough to simply replace the import

NestJS Decorators

• Name: nestjs-decorators
• URL: https://github.com/NeoLabHQ/nestjs-decorators
• Category: Utilities
• GitHub Stars (if applicable): 1
• Why is this resource valuable to the NestJS community?: LLMs currently write a huge amount of code that developers need to read. A big chunk of that code is boilerplate. This library provides decorators for common boilerplate, decreasing the amount of code and making it much easier to read the main business logic, without needing to pay too much attention to side effects like logging.

❤️ Special Note

I have read the contributing guidelines and noticed that maintainers have emphasized multiple times that the library should have at least 10 stars. I would like to ask if you could make an exception. It is quite hard to get even 10 stars for a new repo without adding it to lists such as awesome-nestjs. However, these projects are high quality, well-tested, and actively used in production by our company. If you wouldn't mind taking a look, I am confident you will agree that it would be beneficial to the community to support them in their initial stages of development.