https://github.com/kasir-barati/nestjs-backend-common
All the utility functions and common modules I usually use in my NestJS applications will be published and maintained here.
https://github.com/kasir-barati/nestjs-backend-common
backend javascript library nestjs nodejs npm npm-package pnpm typescript
Last synced: 5 months ago
JSON representation
All the utility functions and common modules I usually use in my NestJS applications will be published and maintained here.
- Host: GitHub
- URL: https://github.com/kasir-barati/nestjs-backend-common
- Owner: kasir-barati
- Created: 2025-04-20T19:26:40.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2026-02-21T23:27:34.000Z (5 months ago)
- Last Synced: 2026-02-21T23:30:45.449Z (5 months ago)
- Topics: backend, javascript, library, nestjs, nodejs, npm, npm-package, pnpm, typescript
- Language: TypeScript
- Homepage: https://kasir-barati.github.io/nestjs-backend-common/
- Size: 210 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
Awesome Lists containing this project
README
# NestJS Backend Common
All the utility functions and common modules I usually use in my NestJS applications will be published and maintained here.
> [!NOTE]
>
> Right now you might need to install `@nestjs/graphql` even though your developing a RESTful API. If that is the case [open an issue](https://github.com/kasir-barati/nestjs-backend-common/issues) with this title: "split package or modularize peer deps" (search for one first though), we can discuss how should we split this library into smaller libraries.
📚 **[View Full API Documentation](https://kasir-barati.github.io/nestjs-backend-common/)**.
📦 **[View the package on NPM](https://www.npmjs.com/package/nestjs-backend-common)**.
## Why `nestjs-cls` Is Peer Dependency?
This is because we wanna share the same storage between our App and this library. Thus we have to define it as peer dependency;
> **Peer Dependencies**: These are dependencies that your project hooks into or modifies in the parent project, usually a plugin for some other library or tool. Peer dependencies are not automatically installed by npm. Instead, they are only checked for, ensuring that the parent project (the project that will depend on your project) has a dependency on the project you hook into. For example, if you create a plugin for a library like Chai, you would specify Chai as a peer dependency. This ensures that the user of your plugin has the correct version of Chai installed.
## FAQ
- NPM ain't installing this library:
```cmd
npm error Cannot read properties of null (reading 'matches')
npm error A complete log of this run can be found in: /home/mjb/.npm/_logs/2026-02-21T20_28_22_477Z-debug-0.log
```
tl;dr would be either remove it from `package.json` and try to install it. Or use pnpm ([learn more](https://github.com/npm/cli/issues/4367#issuecomment-3939448693)).