{"owner":"nestjs","repo":"nest","hasSkills":true,"totalSkillsCount":10,"totalTokensCount":30267,"categories":["plugin-manifest","cursor-rule"],"hasMcp":false,"mcpConfig":null,"found":["packages/common/Readme.md","packages/core/Readme.md","packages/microservices/Readme.md","packages/platform-express/Readme.md","packages/platform-fastify/Readme.md","packages/platform-socket.io/Readme.md","packages/platform-ws/Readme.md","packages/testing/Readme.md","packages/websockets/Readme.md",".cursorrules (nestjs-anti-hallucination-cursorrules-prompt-file.mdc)"],"skills":{"packages/common/Readme.md":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n","packages/core/Readme.md":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n","packages/microservices/Readme.md":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n","packages/platform-express/Readme.md":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n","packages/platform-fastify/Readme.md":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n","packages/platform-socket.io/Readme.md":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n","packages/platform-ws/Readme.md":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n","packages/testing/Readme.md":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n","packages/websockets/Readme.md":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n",".cursorrules (nestjs-anti-hallucination-cursorrules-prompt-file.mdc)":"---\ndescription: \"Cursor rules that block deprecated, phantom, or incorrect NestJS imports, decorators, providers, modules, and testing patterns.\"\nglobs: **/*\nalwaysApply: false\n---\n# NestJS Anti-Hallucination Rules\n\nThese rules OVERRIDE all other generation behavior. Check EVERY line of generated code against these rules.\n\n## Banned Imports & Phantom Packages\n\n### NEVER import these — they don't exist or are deprecated:\n```\n❌ @nestjs/core/decorators — not a real export path\n❌ @nestjs/swagger/decorators — import from @nestjs/swagger directly\n❌ @nestjs/typeorm/repository — not a real export path\n❌ @nestjs/passport/strategies — import from passport-jwt, passport-local, etc.\n❌ @nestjs/bull/decorators — import from @nestjs/bullmq (bull is legacy)\n❌ nestjs-redis — use @nestjs-modules/ioredis or ioredis directly\n❌ @nestjs/cqrs/decorators — import from @nestjs/cqrs directly\n❌ nestjs-config — use @nestjs/config (official)\n❌ nestjs-pino/logger — import from nestjs-pino directly\n```\n\n### Correct import paths:\n```typescript\n// ✅ Swagger\nimport { ApiTags, ApiOperation, ApiResponse } from '@nestjs/swagger';\n\n// ✅ TypeORM\nimport { InjectRepository } from '@nestjs/typeorm';\nimport { Repository, DataSource } from 'typeorm';\n\n// ✅ BullMQ (NOT Bull)\nimport { InjectQueue, Processor, WorkerHost } from '@nestjs/bullmq';\n\n// ✅ Config\nimport { ConfigService, ConfigModule } from '@nestjs/config';\n\n// ✅ Passport\nimport { AuthGuard } from '@nestjs/passport';\nimport { Strategy as JwtStrategy, ExtractJwt } from 'passport-jwt';\n\n// ✅ CQRS\nimport { CommandHandler, ICommandHandler, EventBus } from '@nestjs/cqrs';\n```\n\n## Deprecated Patterns — NEVER Generate These\n\n### 1. getRepository() outside providers\n```typescript\n// ❌ DEPRECATED — removed in TypeORM 0.3+\nconst repo = getRepository(User);\nconst user = await getConnection().getRepository(User).find();\n\n// ✅ CORRECT — inject via constructor\nconstructor(\n @InjectRepository(User)\n private readonly userRepo: Repository,\n) {}\n```\n\n### 2. @nestjs/bull (use @nestjs/bullmq)\n```typescript\n// ❌ OLD — @nestjs/bull with @Process decorator\nimport { Process, Processor } from '@nestjs/bull';\n@Processor('queue')\nclass MyProcessor {\n @Process() async handle(job: Job) {}\n}\n\n// ✅ CURRENT — @nestjs/bullmq with WorkerHost\nimport { Processor, WorkerHost } from '@nestjs/bullmq';\n@Processor('queue')\nclass MyProcessor extends WorkerHost {\n async process(job: Job): Promise {}\n}\n```\n\n### 3. Express-specific middleware mistakes\n```typescript\n// ❌ WRONG — Express req/res types in NestJS\nimport { Request, Response } from 'express';\n@Get()\nasync findAll(@Req() req: Request, @Res() res: Response) {\n res.json(data); // Bypasses interceptors, serialization, exception filters\n}\n\n// ✅ CORRECT — Use NestJS decorators, return values\n@Get()\nasync findAll(@Query() query: FindAllQueryDto): Promise {\n return this.usersService.findAll(query);\n}\n\n// Only use @Res() when streaming files or SSE — add { passthrough: true }\n@Get('download')\nasync download(@Res({ passthrough: true }) res: Response) {\n res.set('Content-Type', 'application/octet-stream');\n return new StreamableFile(stream);\n}\n```\n\n### 4. Wrong decorator combinations\n```typescript\n// ❌ WRONG — @Injectable() on a controller\n@Injectable()\n@Controller('users')\nexport class UsersController {}\n\n// ❌ WRONG — @Controller() on a service\n@Controller()\n@Injectable()\nexport class UsersService {}\n\n// ❌ WRONG — @Body() in a GET handler\n@Get()\nasync findAll(@Body() body: any) {} // GET requests should not have a body\n\n// ❌ WRONG — Both @Param and @Query with same name\n@Get(':id')\nasync findOne(@Param('id') paramId: string, @Query('id') queryId: string) {}\n```\n\n### 5. class-validator / class-transformer mistakes\n```typescript\n// ❌ WRONG — Validation without enabling in main.ts\n// (AI often forgets this critical line)\n// main.ts MUST have:\napp.useGlobalPipes(new ValidationPipe({\n whitelist: true, // Strip unknown properties\n forbidNonWhitelisted: true, // Throw on unknown properties\n transform: true, // Auto-transform payloads to DTO instances\n transformOptions: {\n enableImplicitConversion: true,\n },\n}));\n\n// ❌ WRONG — Mixing validation decorators with wrong transform\nexport class CreateUserDto {\n @IsString()\n name: string;\n\n @IsNumber()\n age: string; // Type mismatch! Decorator says number, type says string\n}\n\n// ✅ CORRECT — Types match decorators\nexport class CreateUserDto {\n @IsString()\n @IsNotEmpty()\n name: string;\n\n @IsInt()\n @Min(0)\n age: number;\n}\n```\n\n### 6. Async module pitfalls\n```typescript\n// ❌ WRONG — useFactory without async when awaiting\nTypeOrmModule.forRootAsync({\n useFactory: (config: ConfigService) => ({\n type: 'postgres',\n url: config.get('DATABASE_URL'), // Not awaited, no inject\n }),\n})\n\n// ✅ CORRECT\nTypeOrmModule.forRootAsync({\n imports: [ConfigModule],\n inject: [ConfigService],\n useFactory: async (config: ConfigService) => ({\n type: 'postgres',\n url: config.getOrThrow('DATABASE_URL'),\n autoLoadEntities: true,\n synchronize: false, // NEVER true in production\n }),\n})\n```\n\n## Type Safety Rules\n\n### NEVER generate `any`\n```typescript\n// ❌ BANNED\ncatch (error: any) { ... }\nconst data: any = await response.json();\nprivate cache = new Map();\n\n// ✅ REQUIRED\ncatch (error: unknown) {\n if (error instanceof DomainError) { ... }\n throw error;\n}\nconst data = await response.json() as PaymentGatewayResponse;\nprivate cache = new Map();\n```\n\n### NEVER generate untyped event payloads\n```typescript\n// ❌ WRONG\neventBus.emit('order.created', { order });\n\n// ✅ CORRECT — Typed events\nexport class OrderCreatedEvent {\n constructor(\n public readonly orderId: string,\n public readonly userId: string,\n public readonly totalAmount: number,\n public readonly occurredAt: Date = new Date(),\n ) {}\n}\neventBus.emit(new OrderCreatedEvent(order.id, order.userId, order.total));\n```\n\n## Configuration Safety\n\n### NEVER generate hardcoded values for:\n- Database connection strings\n- API keys or secrets\n- Port numbers\n- Feature flags\n- External service URLs\n\n### ALWAYS use ConfigService with getOrThrow:\n```typescript\n// ❌ WRONG\nconst port = process.env.PORT || 3000;\nconst dbUrl = process.env.DATABASE_URL;\n\n// ✅ CORRECT\nconst port = this.configService.getOrThrow('app.port');\nconst dbUrl = this.configService.getOrThrow('database.url');\n```\n\n## Database Safety\n\n### NEVER generate:\n```typescript\n// ❌ synchronize: true in production config\n// ❌ DROP TABLE or TRUNCATE in migration files\n// ❌ Raw SQL without parameterized queries\nawait this.dataSource.query(`SELECT * FROM users WHERE id = '${userId}'`); // SQL injection!\n\n// ✅ CORRECT\nawait this.dataSource.query(`SELECT * FROM users WHERE id = $1`, [userId]);\n```\n\n## Remember\n- If you're unsure whether a package exists, DO NOT import it. Ask or check.\n- If you're generating a NestJS pattern you haven't seen in the official docs, STOP and reconsider.\n- When in doubt, generate LESS code with correct patterns rather than MORE code with guesses.\n"},"files":{"packages/common/Readme.md":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n","packages/core/Readme.md":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n","packages/microservices/Readme.md":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n","packages/platform-express/Readme.md":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n","packages/platform-fastify/Readme.md":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n","packages/platform-socket.io/Readme.md":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n","packages/platform-ws/Readme.md":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n","packages/testing/Readme.md":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n","packages/websockets/Readme.md":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n",".cursorrules (nestjs-anti-hallucination-cursorrules-prompt-file.mdc)":"---\ndescription: \"Cursor rules that block deprecated, phantom, or incorrect NestJS imports, decorators, providers, modules, and testing patterns.\"\nglobs: **/*\nalwaysApply: false\n---\n# NestJS Anti-Hallucination Rules\n\nThese rules OVERRIDE all other generation behavior. Check EVERY line of generated code against these rules.\n\n## Banned Imports & Phantom Packages\n\n### NEVER import these — they don't exist or are deprecated:\n```\n❌ @nestjs/core/decorators — not a real export path\n❌ @nestjs/swagger/decorators — import from @nestjs/swagger directly\n❌ @nestjs/typeorm/repository — not a real export path\n❌ @nestjs/passport/strategies — import from passport-jwt, passport-local, etc.\n❌ @nestjs/bull/decorators — import from @nestjs/bullmq (bull is legacy)\n❌ nestjs-redis — use @nestjs-modules/ioredis or ioredis directly\n❌ @nestjs/cqrs/decorators — import from @nestjs/cqrs directly\n❌ nestjs-config — use @nestjs/config (official)\n❌ nestjs-pino/logger — import from nestjs-pino directly\n```\n\n### Correct import paths:\n```typescript\n// ✅ Swagger\nimport { ApiTags, ApiOperation, ApiResponse } from '@nestjs/swagger';\n\n// ✅ TypeORM\nimport { InjectRepository } from '@nestjs/typeorm';\nimport { Repository, DataSource } from 'typeorm';\n\n// ✅ BullMQ (NOT Bull)\nimport { InjectQueue, Processor, WorkerHost } from '@nestjs/bullmq';\n\n// ✅ Config\nimport { ConfigService, ConfigModule } from '@nestjs/config';\n\n// ✅ Passport\nimport { AuthGuard } from '@nestjs/passport';\nimport { Strategy as JwtStrategy, ExtractJwt } from 'passport-jwt';\n\n// ✅ CQRS\nimport { CommandHandler, ICommandHandler, EventBus } from '@nestjs/cqrs';\n```\n\n## Deprecated Patterns — NEVER Generate These\n\n### 1. getRepository() outside providers\n```typescript\n// ❌ DEPRECATED — removed in TypeORM 0.3+\nconst repo = getRepository(User);\nconst user = await getConnection().getRepository(User).find();\n\n// ✅ CORRECT — inject via constructor\nconstructor(\n @InjectRepository(User)\n private readonly userRepo: Repository,\n) {}\n```\n\n### 2. @nestjs/bull (use @nestjs/bullmq)\n```typescript\n// ❌ OLD — @nestjs/bull with @Process decorator\nimport { Process, Processor } from '@nestjs/bull';\n@Processor('queue')\nclass MyProcessor {\n @Process() async handle(job: Job) {}\n}\n\n// ✅ CURRENT — @nestjs/bullmq with WorkerHost\nimport { Processor, WorkerHost } from '@nestjs/bullmq';\n@Processor('queue')\nclass MyProcessor extends WorkerHost {\n async process(job: Job): Promise {}\n}\n```\n\n### 3. Express-specific middleware mistakes\n```typescript\n// ❌ WRONG — Express req/res types in NestJS\nimport { Request, Response } from 'express';\n@Get()\nasync findAll(@Req() req: Request, @Res() res: Response) {\n res.json(data); // Bypasses interceptors, serialization, exception filters\n}\n\n// ✅ CORRECT — Use NestJS decorators, return values\n@Get()\nasync findAll(@Query() query: FindAllQueryDto): Promise {\n return this.usersService.findAll(query);\n}\n\n// Only use @Res() when streaming files or SSE — add { passthrough: true }\n@Get('download')\nasync download(@Res({ passthrough: true }) res: Response) {\n res.set('Content-Type', 'application/octet-stream');\n return new StreamableFile(stream);\n}\n```\n\n### 4. Wrong decorator combinations\n```typescript\n// ❌ WRONG — @Injectable() on a controller\n@Injectable()\n@Controller('users')\nexport class UsersController {}\n\n// ❌ WRONG — @Controller() on a service\n@Controller()\n@Injectable()\nexport class UsersService {}\n\n// ❌ WRONG — @Body() in a GET handler\n@Get()\nasync findAll(@Body() body: any) {} // GET requests should not have a body\n\n// ❌ WRONG — Both @Param and @Query with same name\n@Get(':id')\nasync findOne(@Param('id') paramId: string, @Query('id') queryId: string) {}\n```\n\n### 5. class-validator / class-transformer mistakes\n```typescript\n// ❌ WRONG — Validation without enabling in main.ts\n// (AI often forgets this critical line)\n// main.ts MUST have:\napp.useGlobalPipes(new ValidationPipe({\n whitelist: true, // Strip unknown properties\n forbidNonWhitelisted: true, // Throw on unknown properties\n transform: true, // Auto-transform payloads to DTO instances\n transformOptions: {\n enableImplicitConversion: true,\n },\n}));\n\n// ❌ WRONG — Mixing validation decorators with wrong transform\nexport class CreateUserDto {\n @IsString()\n name: string;\n\n @IsNumber()\n age: string; // Type mismatch! Decorator says number, type says string\n}\n\n// ✅ CORRECT — Types match decorators\nexport class CreateUserDto {\n @IsString()\n @IsNotEmpty()\n name: string;\n\n @IsInt()\n @Min(0)\n age: number;\n}\n```\n\n### 6. Async module pitfalls\n```typescript\n// ❌ WRONG — useFactory without async when awaiting\nTypeOrmModule.forRootAsync({\n useFactory: (config: ConfigService) => ({\n type: 'postgres',\n url: config.get('DATABASE_URL'), // Not awaited, no inject\n }),\n})\n\n// ✅ CORRECT\nTypeOrmModule.forRootAsync({\n imports: [ConfigModule],\n inject: [ConfigService],\n useFactory: async (config: ConfigService) => ({\n type: 'postgres',\n url: config.getOrThrow('DATABASE_URL'),\n autoLoadEntities: true,\n synchronize: false, // NEVER true in production\n }),\n})\n```\n\n## Type Safety Rules\n\n### NEVER generate `any`\n```typescript\n// ❌ BANNED\ncatch (error: any) { ... }\nconst data: any = await response.json();\nprivate cache = new Map();\n\n// ✅ REQUIRED\ncatch (error: unknown) {\n if (error instanceof DomainError) { ... }\n throw error;\n}\nconst data = await response.json() as PaymentGatewayResponse;\nprivate cache = new Map();\n```\n\n### NEVER generate untyped event payloads\n```typescript\n// ❌ WRONG\neventBus.emit('order.created', { order });\n\n// ✅ CORRECT — Typed events\nexport class OrderCreatedEvent {\n constructor(\n public readonly orderId: string,\n public readonly userId: string,\n public readonly totalAmount: number,\n public readonly occurredAt: Date = new Date(),\n ) {}\n}\neventBus.emit(new OrderCreatedEvent(order.id, order.userId, order.total));\n```\n\n## Configuration Safety\n\n### NEVER generate hardcoded values for:\n- Database connection strings\n- API keys or secrets\n- Port numbers\n- Feature flags\n- External service URLs\n\n### ALWAYS use ConfigService with getOrThrow:\n```typescript\n// ❌ WRONG\nconst port = process.env.PORT || 3000;\nconst dbUrl = process.env.DATABASE_URL;\n\n// ✅ CORRECT\nconst port = this.configService.getOrThrow('app.port');\nconst dbUrl = this.configService.getOrThrow('database.url');\n```\n\n## Database Safety\n\n### NEVER generate:\n```typescript\n// ❌ synchronize: true in production config\n// ❌ DROP TABLE or TRUNCATE in migration files\n// ❌ Raw SQL without parameterized queries\nawait this.dataSource.query(`SELECT * FROM users WHERE id = '${userId}'`); // SQL injection!\n\n// ✅ CORRECT\nawait this.dataSource.query(`SELECT * FROM users WHERE id = $1`, [userId]);\n```\n\n## Remember\n- If you're unsure whether a package exists, DO NOT import it. Ask or check.\n- If you're generating a NestJS pattern you haven't seen in the official docs, STOP and reconsider.\n- When in doubt, generate LESS code with correct patterns rather than MORE code with guesses.\n"},"items":[{"name":"Readme.md","path":"packages/common/Readme.md","rawUrl":"https://raw.githubusercontent.com/nestjs/nest/HEAD/packages/common/Readme.md","title":"common Documentation","category":"plugin-manifest","format":"markdown","content":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n","isInternal":false,"tokens":3169,"sizeBytes":11493},{"name":"Readme.md","path":"packages/core/Readme.md","rawUrl":"https://raw.githubusercontent.com/nestjs/nest/HEAD/packages/core/Readme.md","title":"core Documentation","category":"plugin-manifest","format":"markdown","content":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n","isInternal":false,"tokens":3169,"sizeBytes":11493},{"name":"Readme.md","path":"packages/microservices/Readme.md","rawUrl":"https://raw.githubusercontent.com/nestjs/nest/HEAD/packages/microservices/Readme.md","title":"microservices Documentation","category":"plugin-manifest","format":"markdown","content":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n","isInternal":false,"tokens":3169,"sizeBytes":11493},{"name":"Readme.md","path":"packages/platform-express/Readme.md","rawUrl":"https://raw.githubusercontent.com/nestjs/nest/HEAD/packages/platform-express/Readme.md","title":"platform-express Documentation","category":"plugin-manifest","format":"markdown","content":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n","isInternal":false,"tokens":3169,"sizeBytes":11493},{"name":"Readme.md","path":"packages/platform-fastify/Readme.md","rawUrl":"https://raw.githubusercontent.com/nestjs/nest/HEAD/packages/platform-fastify/Readme.md","title":"platform-fastify Documentation","category":"plugin-manifest","format":"markdown","content":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n","isInternal":false,"tokens":3169,"sizeBytes":11493},{"name":"Readme.md","path":"packages/platform-socket.io/Readme.md","rawUrl":"https://raw.githubusercontent.com/nestjs/nest/HEAD/packages/platform-socket.io/Readme.md","title":"platform-socket.io Documentation","category":"plugin-manifest","format":"markdown","content":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n","isInternal":false,"tokens":3169,"sizeBytes":11493},{"name":"Readme.md","path":"packages/platform-ws/Readme.md","rawUrl":"https://raw.githubusercontent.com/nestjs/nest/HEAD/packages/platform-ws/Readme.md","title":"platform-ws Documentation","category":"plugin-manifest","format":"markdown","content":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n","isInternal":false,"tokens":3169,"sizeBytes":11493},{"name":"Readme.md","path":"packages/testing/Readme.md","rawUrl":"https://raw.githubusercontent.com/nestjs/nest/HEAD/packages/testing/Readme.md","title":"testing Documentation","category":"plugin-manifest","format":"markdown","content":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n","isInternal":false,"tokens":3169,"sizeBytes":11493},{"name":"Readme.md","path":"packages/websockets/Readme.md","rawUrl":"https://raw.githubusercontent.com/nestjs/nest/HEAD/packages/websockets/Readme.md","title":"websockets Documentation","category":"plugin-manifest","format":"markdown","content":"

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n","isInternal":false,"tokens":3169,"sizeBytes":11493},{"name":".cursorrules","path":".cursorrules (nestjs-anti-hallucination-cursorrules-prompt-file.mdc)","rawUrl":"https://raw.githubusercontent.com/PatrickJS/awesome-cursorrules/main/rules/nestjs-anti-hallucination-cursorrules-prompt-file.mdc","title":"Awesome Cursorrules: nestjs anti hallucination","category":"cursor-rule","format":"markdown","content":"---\ndescription: \"Cursor rules that block deprecated, phantom, or incorrect NestJS imports, decorators, providers, modules, and testing patterns.\"\nglobs: **/*\nalwaysApply: false\n---\n# NestJS Anti-Hallucination Rules\n\nThese rules OVERRIDE all other generation behavior. Check EVERY line of generated code against these rules.\n\n## Banned Imports & Phantom Packages\n\n### NEVER import these — they don't exist or are deprecated:\n```\n❌ @nestjs/core/decorators — not a real export path\n❌ @nestjs/swagger/decorators — import from @nestjs/swagger directly\n❌ @nestjs/typeorm/repository — not a real export path\n❌ @nestjs/passport/strategies — import from passport-jwt, passport-local, etc.\n❌ @nestjs/bull/decorators — import from @nestjs/bullmq (bull is legacy)\n❌ nestjs-redis — use @nestjs-modules/ioredis or ioredis directly\n❌ @nestjs/cqrs/decorators — import from @nestjs/cqrs directly\n❌ nestjs-config — use @nestjs/config (official)\n❌ nestjs-pino/logger — import from nestjs-pino directly\n```\n\n### Correct import paths:\n```typescript\n// ✅ Swagger\nimport { ApiTags, ApiOperation, ApiResponse } from '@nestjs/swagger';\n\n// ✅ TypeORM\nimport { InjectRepository } from '@nestjs/typeorm';\nimport { Repository, DataSource } from 'typeorm';\n\n// ✅ BullMQ (NOT Bull)\nimport { InjectQueue, Processor, WorkerHost } from '@nestjs/bullmq';\n\n// ✅ Config\nimport { ConfigService, ConfigModule } from '@nestjs/config';\n\n// ✅ Passport\nimport { AuthGuard } from '@nestjs/passport';\nimport { Strategy as JwtStrategy, ExtractJwt } from 'passport-jwt';\n\n// ✅ CQRS\nimport { CommandHandler, ICommandHandler, EventBus } from '@nestjs/cqrs';\n```\n\n## Deprecated Patterns — NEVER Generate These\n\n### 1. getRepository() outside providers\n```typescript\n// ❌ DEPRECATED — removed in TypeORM 0.3+\nconst repo = getRepository(User);\nconst user = await getConnection().getRepository(User).find();\n\n// ✅ CORRECT — inject via constructor\nconstructor(\n @InjectRepository(User)\n private readonly userRepo: Repository,\n) {}\n```\n\n### 2. @nestjs/bull (use @nestjs/bullmq)\n```typescript\n// ❌ OLD — @nestjs/bull with @Process decorator\nimport { Process, Processor } from '@nestjs/bull';\n@Processor('queue')\nclass MyProcessor {\n @Process() async handle(job: Job) {}\n}\n\n// ✅ CURRENT — @nestjs/bullmq with WorkerHost\nimport { Processor, WorkerHost } from '@nestjs/bullmq';\n@Processor('queue')\nclass MyProcessor extends WorkerHost {\n async process(job: Job): Promise {}\n}\n```\n\n### 3. Express-specific middleware mistakes\n```typescript\n// ❌ WRONG — Express req/res types in NestJS\nimport { Request, Response } from 'express';\n@Get()\nasync findAll(@Req() req: Request, @Res() res: Response) {\n res.json(data); // Bypasses interceptors, serialization, exception filters\n}\n\n// ✅ CORRECT — Use NestJS decorators, return values\n@Get()\nasync findAll(@Query() query: FindAllQueryDto): Promise {\n return this.usersService.findAll(query);\n}\n\n// Only use @Res() when streaming files or SSE — add { passthrough: true }\n@Get('download')\nasync download(@Res({ passthrough: true }) res: Response) {\n res.set('Content-Type', 'application/octet-stream');\n return new StreamableFile(stream);\n}\n```\n\n### 4. Wrong decorator combinations\n```typescript\n// ❌ WRONG — @Injectable() on a controller\n@Injectable()\n@Controller('users')\nexport class UsersController {}\n\n// ❌ WRONG — @Controller() on a service\n@Controller()\n@Injectable()\nexport class UsersService {}\n\n// ❌ WRONG — @Body() in a GET handler\n@Get()\nasync findAll(@Body() body: any) {} // GET requests should not have a body\n\n// ❌ WRONG — Both @Param and @Query with same name\n@Get(':id')\nasync findOne(@Param('id') paramId: string, @Query('id') queryId: string) {}\n```\n\n### 5. class-validator / class-transformer mistakes\n```typescript\n// ❌ WRONG — Validation without enabling in main.ts\n// (AI often forgets this critical line)\n// main.ts MUST have:\napp.useGlobalPipes(new ValidationPipe({\n whitelist: true, // Strip unknown properties\n forbidNonWhitelisted: true, // Throw on unknown properties\n transform: true, // Auto-transform payloads to DTO instances\n transformOptions: {\n enableImplicitConversion: true,\n },\n}));\n\n// ❌ WRONG — Mixing validation decorators with wrong transform\nexport class CreateUserDto {\n @IsString()\n name: string;\n\n @IsNumber()\n age: string; // Type mismatch! Decorator says number, type says string\n}\n\n// ✅ CORRECT — Types match decorators\nexport class CreateUserDto {\n @IsString()\n @IsNotEmpty()\n name: string;\n\n @IsInt()\n @Min(0)\n age: number;\n}\n```\n\n### 6. Async module pitfalls\n```typescript\n// ❌ WRONG — useFactory without async when awaiting\nTypeOrmModule.forRootAsync({\n useFactory: (config: ConfigService) => ({\n type: 'postgres',\n url: config.get('DATABASE_URL'), // Not awaited, no inject\n }),\n})\n\n// ✅ CORRECT\nTypeOrmModule.forRootAsync({\n imports: [ConfigModule],\n inject: [ConfigService],\n useFactory: async (config: ConfigService) => ({\n type: 'postgres',\n url: config.getOrThrow('DATABASE_URL'),\n autoLoadEntities: true,\n synchronize: false, // NEVER true in production\n }),\n})\n```\n\n## Type Safety Rules\n\n### NEVER generate `any`\n```typescript\n// ❌ BANNED\ncatch (error: any) { ... }\nconst data: any = await response.json();\nprivate cache = new Map();\n\n// ✅ REQUIRED\ncatch (error: unknown) {\n if (error instanceof DomainError) { ... }\n throw error;\n}\nconst data = await response.json() as PaymentGatewayResponse;\nprivate cache = new Map();\n```\n\n### NEVER generate untyped event payloads\n```typescript\n// ❌ WRONG\neventBus.emit('order.created', { order });\n\n// ✅ CORRECT — Typed events\nexport class OrderCreatedEvent {\n constructor(\n public readonly orderId: string,\n public readonly userId: string,\n public readonly totalAmount: number,\n public readonly occurredAt: Date = new Date(),\n ) {}\n}\neventBus.emit(new OrderCreatedEvent(order.id, order.userId, order.total));\n```\n\n## Configuration Safety\n\n### NEVER generate hardcoded values for:\n- Database connection strings\n- API keys or secrets\n- Port numbers\n- Feature flags\n- External service URLs\n\n### ALWAYS use ConfigService with getOrThrow:\n```typescript\n// ❌ WRONG\nconst port = process.env.PORT || 3000;\nconst dbUrl = process.env.DATABASE_URL;\n\n// ✅ CORRECT\nconst port = this.configService.getOrThrow('app.port');\nconst dbUrl = this.configService.getOrThrow('database.url');\n```\n\n## Database Safety\n\n### NEVER generate:\n```typescript\n// ❌ synchronize: true in production config\n// ❌ DROP TABLE or TRUNCATE in migration files\n// ❌ Raw SQL without parameterized queries\nawait this.dataSource.query(`SELECT * FROM users WHERE id = '${userId}'`); // SQL injection!\n\n// ✅ CORRECT\nawait this.dataSource.query(`SELECT * FROM users WHERE id = $1`, [userId]);\n```\n\n## Remember\n- If you're unsure whether a package exists, DO NOT import it. Ask or check.\n- If you're generating a NestJS pattern you haven't seen in the official docs, STOP and reconsider.\n- When in doubt, generate LESS code with correct patterns rather than MORE code with guesses.\n","tokens":1746,"sizeBytes":7276}],"systemPromptSnippet":"\n\n

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n\n\n

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n\n\n

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n\n\n

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n\n\n

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n\n\n

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n\n\n

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n\n\n

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n\n\n

\n \"Nest\n

\n\n[circleci-image]: https://img.shields.io/circleci/build/github/nestjs/nest/master?token=abc123def456\n[circleci-url]: https://circleci.com/gh/nestjs/nest\n\n

A progressive Node.js framework for building efficient and scalable server-side applications.

\n

\n\"NPM\n\"Package\n\"NPM\n\"CircleCI\"\n\"Discord\"/\n\"Backers\n\"Sponsors\n \n \"Support\n \n

\n \n\n## Description\n\nNest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).\n\n

Under the hood, Nest makes use of Express, but also provides compatibility with a wide range of other libraries, like Fastify, allowing for easy use of the myriad of third-party plugins which are available.

\n\n## Philosophy\n\n

In recent years, thanks to Node.js, JavaScript has become the “lingua franca” of the web for both front-end and back-end applications, giving rise to awesome projects like Angular, React, and Vue, which improve developer productivity and enable the construction of fast, testable, and extensible frontend applications. However, on the server-side, while there are a lot of superb libraries, helpers, and tools for Node, none of them effectively solve the main problem - the architecture.

\n

Nest aims to provide an application architecture out of the box which allows for effortless creation of highly testable, scalable, and loosely coupled and easily maintainable applications. The architecture is heavily inspired by Angular.

\n\n## Getting started\n\n- To check out the [guide](https://docs.nestjs.com), visit [docs.nestjs.com](https://docs.nestjs.com). :books:\n- 要查看中文 [指南](readme_zh.md), 请访问 [docs.nestjs.cn](https://docs.nestjs.cn). :books:\n- [가이드](readme_kr.md) 문서는 [docs.nestjs.com](https://docs.nestjs.com)에서 확인하실 수 있습니다. :books:\n- [ガイド](readme_jp.md)は [docs.nestjs.com](https://docs.nestjs.com)でご確認ください。 :books:\n\n## Questions\n\nFor questions and support please use the official [Discord channel](https://discord.gg/G7Qnnhy). The issue list of this repo is **exclusively** for bug reports and feature requests.\n\n## Issues\n\nPlease make sure to read the [Issue Reporting Checklist](https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md#-submitting-an-issue) before opening an issue. Issues not conforming to the guidelines may be closed immediately.\n\n## Observability\n\n[NestJS Observe](https://observe.nestjs.com) is the official observability platform for Nest applications. Install the `@nestjs/observe` SDK, pass an API key, and requests, background jobs, errors, logs, and distributed traces start streaming to a dashboard - no manual span wiring and no collector to run. Because the SDK hooks into Nest's own request lifecycle, a trace reads like a call graph of your controllers and providers instead of a bare HTTP route. Free for up to 300,000 events a month, and there is a [live demo](https://www.observe-demo.nestjs.com/dashboard) with no signup.\n\n## Consulting\n\nWith official support, you can get expert help straight from the Nest core team. We provide dedicated technical support, migration strategies, advice on best practices (and design decisions), PR reviews, and team augmentation. Read more about [support here](https://enterprise.nestjs.com).\n\n## Support\n\nNest is an MIT-licensed open source project. It can grow thanks to the sponsors and support from the amazing backers. If you'd like to join them, please [read more here](https://docs.nestjs.com/support).\n\n#### Principal Sponsors\n\n\n\n\n\n\n\n\n\n
\n\n#### Gold Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Silver Sponsors\n\n\n\n\n\n\n\n\n\n\n\n\n\n
\n\n#### Sponsors\n\n\n\n\n\n\n\n\n\n
\n
\n\n## Backers\n\n\n\n## Stay in touch\n\n- Author - [Kamil Myśliwiec](https://x.com/kammysliwiec)\n- Website - [https://nestjs.com](https://nestjs.com/)\n- X - [@nestframework](https://x.com/nestframework)\n\n## License\n\nNest is [MIT licensed](LICENSE).\n\n\n---\ndescription: \"Cursor rules that block deprecated, phantom, or incorrect NestJS imports, decorators, providers, modules, and testing patterns.\"\nglobs: **/*\nalwaysApply: false\n---\n# NestJS Anti-Hallucination Rules\n\nThese rules OVERRIDE all other generation behavior. Check EVERY line of generated code against these rules.\n\n## Banned Imports & Phantom Packages\n\n### NEVER import these — they don't exist or are deprecated:\n```\n❌ @nestjs/core/decorators — not a real export path\n❌ @nestjs/swagger/decorators — import from @nestjs/swagger directly\n❌ @nestjs/typeorm/repository — not a real export path\n❌ @nestjs/passport/strategies — import from passport-jwt, passport-local, etc.\n❌ @nestjs/bull/decorators — import from @nestjs/bullmq (bull is legacy)\n❌ nestjs-redis — use @nestjs-modules/ioredis or ioredis directly\n❌ @nestjs/cqrs/decorators — import from @nestjs/cqrs directly\n❌ nestjs-config — use @nestjs/config (official)\n❌ nestjs-pino/logger — import from nestjs-pino directly\n```\n\n### Correct import paths:\n```typescript\n// ✅ Swagger\nimport { ApiTags, ApiOperation, ApiResponse } from '@nestjs/swagger';\n\n// ✅ TypeORM\nimport { InjectRepository } from '@nestjs/typeorm';\nimport { Repository, DataSource } from 'typeorm';\n\n// ✅ BullMQ (NOT Bull)\nimport { InjectQueue, Processor, WorkerHost } from '@nestjs/bullmq';\n\n// ✅ Config\nimport { ConfigService, ConfigModule } from '@nestjs/config';\n\n// ✅ Passport\nimport { AuthGuard } from '@nestjs/passport';\nimport { Strategy as JwtStrategy, ExtractJwt } from 'passport-jwt';\n\n// ✅ CQRS\nimport { CommandHandler, ICommandHandler, EventBus } from '@nestjs/cqrs';\n```\n\n## Deprecated Patterns — NEVER Generate These\n\n### 1. getRepository() outside providers\n```typescript\n// ❌ DEPRECATED — removed in TypeORM 0.3+\nconst repo = getRepository(User);\nconst user = await getConnection().getRepository(User).find();\n\n// ✅ CORRECT — inject via constructor\nconstructor(\n @InjectRepository(User)\n private readonly userRepo: Repository,\n) {}\n```\n\n### 2. @nestjs/bull (use @nestjs/bullmq)\n```typescript\n// ❌ OLD — @nestjs/bull with @Process decorator\nimport { Process, Processor } from '@nestjs/bull';\n@Processor('queue')\nclass MyProcessor {\n @Process() async handle(job: Job) {}\n}\n\n// ✅ CURRENT — @nestjs/bullmq with WorkerHost\nimport { Processor, WorkerHost } from '@nestjs/bullmq';\n@Processor('queue')\nclass MyProcessor extends WorkerHost {\n async process(job: Job): Promise {}\n}\n```\n\n### 3. Express-specific middleware mistakes\n```typescript\n// ❌ WRONG — Express req/res types in NestJS\nimport { Request, Response } from 'express';\n@Get()\nasync findAll(@Req() req: Request, @Res() res: Response) {\n res.json(data); // Bypasses interceptors, serialization, exception filters\n}\n\n// ✅ CORRECT — Use NestJS decorators, return values\n@Get()\nasync findAll(@Query() query: FindAllQueryDto): Promise {\n return this.usersService.findAll(query);\n}\n\n// Only use @Res() when streaming files or SSE — add { passthrough: true }\n@Get('download')\nasync download(@Res({ passthrough: true }) res: Response) {\n res.set('Content-Type', 'application/octet-stream');\n return new StreamableFile(stream);\n}\n```\n\n### 4. Wrong decorator combinations\n```typescript\n// ❌ WRONG — @Injectable() on a controller\n@Injectable()\n@Controller('users')\nexport class UsersController {}\n\n// ❌ WRONG — @Controller() on a service\n@Controller()\n@Injectable()\nexport class UsersService {}\n\n// ❌ WRONG — @Body() in a GET handler\n@Get()\nasync findAll(@Body() body: any) {} // GET requests should not have a body\n\n// ❌ WRONG — Both @Param and @Query with same name\n@Get(':id')\nasync findOne(@Param('id') paramId: string, @Query('id') queryId: string) {}\n```\n\n### 5. class-validator / class-transformer mistakes\n```typescript\n// ❌ WRONG — Validation without enabling in main.ts\n// (AI often forgets this critical line)\n// main.ts MUST have:\napp.useGlobalPipes(new ValidationPipe({\n whitelist: true, // Strip unknown properties\n forbidNonWhitelisted: true, // Throw on unknown properties\n transform: true, // Auto-transform payloads to DTO instances\n transformOptions: {\n enableImplicitConversion: true,\n },\n}));\n\n// ❌ WRONG — Mixing validation decorators with wrong transform\nexport class CreateUserDto {\n @IsString()\n name: string;\n\n @IsNumber()\n age: string; // Type mismatch! Decorator says number, type says string\n}\n\n// ✅ CORRECT — Types match decorators\nexport class CreateUserDto {\n @IsString()\n @IsNotEmpty()\n name: string;\n\n @IsInt()\n @Min(0)\n age: number;\n}\n```\n\n### 6. Async module pitfalls\n```typescript\n// ❌ WRONG — useFactory without async when awaiting\nTypeOrmModule.forRootAsync({\n useFactory: (config: ConfigService) => ({\n type: 'postgres',\n url: config.get('DATABASE_URL'), // Not awaited, no inject\n }),\n})\n\n// ✅ CORRECT\nTypeOrmModule.forRootAsync({\n imports: [ConfigModule],\n inject: [ConfigService],\n useFactory: async (config: ConfigService) => ({\n type: 'postgres',\n url: config.getOrThrow('DATABASE_URL'),\n autoLoadEntities: true,\n synchronize: false, // NEVER true in production\n }),\n})\n```\n\n## Type Safety Rules\n\n### NEVER generate `any`\n```typescript\n// ❌ BANNED\ncatch (error: any) { ... }\nconst data: any = await response.json();\nprivate cache = new Map();\n\n// ✅ REQUIRED\ncatch (error: unknown) {\n if (error instanceof DomainError) { ... }\n throw error;\n}\nconst data = await response.json() as PaymentGatewayResponse;\nprivate cache = new Map();\n```\n\n### NEVER generate untyped event payloads\n```typescript\n// ❌ WRONG\neventBus.emit('order.created', { order });\n\n// ✅ CORRECT — Typed events\nexport class OrderCreatedEvent {\n constructor(\n public readonly orderId: string,\n public readonly userId: string,\n public readonly totalAmount: number,\n public readonly occurredAt: Date = new Date(),\n ) {}\n}\neventBus.emit(new OrderCreatedEvent(order.id, order.userId, order.total));\n```\n\n## Configuration Safety\n\n### NEVER generate hardcoded values for:\n- Database connection strings\n- API keys or secrets\n- Port numbers\n- Feature flags\n- External service URLs\n\n### ALWAYS use ConfigService with getOrThrow:\n```typescript\n// ❌ WRONG\nconst port = process.env.PORT || 3000;\nconst dbUrl = process.env.DATABASE_URL;\n\n// ✅ CORRECT\nconst port = this.configService.getOrThrow('app.port');\nconst dbUrl = this.configService.getOrThrow('database.url');\n```\n\n## Database Safety\n\n### NEVER generate:\n```typescript\n// ❌ synchronize: true in production config\n// ❌ DROP TABLE or TRUNCATE in migration files\n// ❌ Raw SQL without parameterized queries\nawait this.dataSource.query(`SELECT * FROM users WHERE id = '${userId}'`); // SQL injection!\n\n// ✅ CORRECT\nawait this.dataSource.query(`SELECT * FROM users WHERE id = $1`, [userId]);\n```\n\n## Remember\n- If you're unsure whether a package exists, DO NOT import it. Ask or check.\n- If you're generating a NestJS pattern you haven't seen in the official docs, STOP and reconsider.\n- When in doubt, generate LESS code with correct patterns rather than MORE code with guesses.\n"}