Skip to content

ever-co/ever-works / .agents/skills/nestjs-best-practices

nestjs-best-practices

Verified

NestJS best practices and architecture patterns for building production-ready applications. This skill should be used when writing, reviewing, or refactoring NestJS code to ensure proper patterns for modules, dependency injection, security, and performance.

FileKindSize
AGENTS.mdmarkdown154.2 KB
README.mdmarkdown4.7 KB
SKILL.mdskill md4.8 KB
rules/_sections.mdmarkdown2.1 KB
rules/_template.mdmarkdown633 B
rules/api-use-dto-serialization.mdmarkdown4.2 KB
rules/api-use-interceptors.mdmarkdown5.4 KB
rules/api-use-pipes.mdmarkdown5.3 KB
rules/api-versioning.mdmarkdown4.7 KB
rules/arch-avoid-circular-deps.mdmarkdown1.9 KB
rules/arch-feature-modules.mdmarkdown2.3 KB
rules/arch-module-sharing.mdmarkdown3.7 KB
rules/arch-single-responsibility.mdmarkdown2.8 KB
rules/arch-use-events.mdmarkdown2.9 KB
rules/arch-use-repository-pattern.mdmarkdown2.7 KB
rules/db-avoid-n-plus-one.mdmarkdown3.8 KB
rules/db-use-migrations.mdmarkdown3.7 KB
rules/db-use-transactions.mdmarkdown3.6 KB
rules/devops-graceful-shutdown.mdmarkdown5.5 KB
rules/devops-use-config-module.mdmarkdown4.2 KB
rules/devops-use-logging.mdmarkdown5.1 KB
rules/di-avoid-service-locator.mdmarkdown2.8 KB
rules/di-interface-segregation.mdmarkdown5.0 KB
rules/di-liskov-substitution.mdmarkdown6.8 KB
rules/di-prefer-constructor-injection.mdmarkdown2.2 KB
rules/di-scope-awareness.mdmarkdown2.5 KB
rules/di-use-interfaces-tokens.mdmarkdown2.5 KB
rules/error-handle-async-errors.mdmarkdown3.4 KB
rules/error-throw-http-exceptions.mdmarkdown3.0 KB
rules/error-use-exception-filters.mdmarkdown3.4 KB
rules/micro-use-health-checks.mdmarkdown6.1 KB
rules/micro-use-patterns.mdmarkdown5.0 KB
rules/micro-use-queues.mdmarkdown5.7 KB
rules/perf-async-hooks.mdmarkdown2.8 KB
rules/perf-lazy-loading.mdmarkdown3.6 KB
rules/perf-optimize-database.mdmarkdown3.0 KB
rules/perf-use-caching.mdmarkdown3.3 KB
rules/security-auth-jwt.mdmarkdown3.8 KB
rules/security-rate-limiting.mdmarkdown3.1 KB
rules/security-sanitize-output.mdmarkdown3.7 KB
rules/security-use-guards.mdmarkdown3.4 KB
rules/security-validate-all-input.mdmarkdown3.2 KB
rules/test-e2e-supertest.mdmarkdown4.4 KB
rules/test-mock-external-services.mdmarkdown4.2 KB
rules/test-use-testing-module.mdmarkdown4.1 KB
scripts/build-agents.tsscript8.1 KB
scripts/build.shscript369 B
scripts/package-lock.jsonmanifest7.7 KB
scripts/package.jsonmanifest410 B

rules/devops-use-logging.md

View on GitHub
---
title: Use Structured Logging
impact: MEDIUM-HIGH
impactDescription: Structured logging enables effective debugging and monitoring
tags: devops, logging, structured-logs, pino
---

## Use Structured Logging

Use NestJS Logger with structured JSON output in production. Include contextual information (request ID, user ID, operation) to trace requests across services. Avoid console.log and implement proper log levels.

**Incorrect (using console.log in production):**

```typescript
// Use console.log in production
@Injectable()
export class UsersService {
	async createUser(dto: CreateUserDto): Promise<User> {
		console.log('Creating user:', dto);
		// Not structured, no levels, lost in production logs

		try {
			const user = await this.repo.save(dto);
			console.log('User created:', user.id);
			return user;
		} catch (error) {
			console.log('Error:', error); // Using log for errors
			throw error;
		}
	}
}

// Log sensitive data
console.log('Login attempt:', { email, password }); // SECURITY RISK!

// Inconsistent log format
logger.log('User ' + userId + ' created at ' + new Date());
// Hard to parse, no structure
```

**Correct (use structured logging with context):**

```typescript
// Configure logger in main.ts
async function bootstrap() {
	const app = await NestFactory.create(AppModule, {
		logger:
			process.env.NODE_ENV === 'production'
				? ['error', 'warn', 'log']
				: ['error', 'warn', 'log', 'debug', 'verbose']
	});
}

// Use NestJS Logger with context
@Injectable()
export class UsersService {
	private readonly logger = new Logger(UsersService.name);

	async createUser(dto: CreateUserDto): Promise<User> {
		this.logger.log('Creating user', { email: dto.email });

		try {
			const user = await this.repo.save(dto);
			this.logger.log('User created', { userId: user.id });
			return user;
		} catch (error) {
			this.logger.error('Failed to create user', error.stack, {
				email: dto.email
			});
			throw error;
		}
	}
}

// Custom logger for JSON output
@Injectable()
export class JsonLogger implements LoggerService {
	log(message: string, context?: object): void {
		console.log(
			JSON.stringify({
				level: 'info',
				timestamp: new Date().toISOString(),
				message,
				...context
			})
		);
	}

	error(message: string, trace?: string, context?: object): void {
		console.error(
			JSON.stringify({
				level: 'error',
				timestamp: new Date().toISOString(),
				message,
				trace,
				...context
			})
		);
	}

	warn(message: string, context?: object): void {
		console.warn(
			JSON.stringify({
				level: 'warn',
				timestamp: new Date().toISOString(),
				message,
				...context
			})
		);
	}

	debug(message: string, context?: object): void {
		console.debug(
			JSON.stringify({
				level: 'debug',
				timestamp: new Date().toISOString(),
				message,
				...context
			})
		);
	}
}

// Request context logging with ClsModule
import { ClsModule, ClsService } from 'nestjs-cls';

@Module({
	imports: [
		ClsModule.forRoot({
			global: true,
			middleware: {
				mount: true,
				generateId: true
			}
		})
	]
})
export class AppModule {}

// Middleware to set request context
@Injectable()
export class RequestContextMiddleware implements NestMiddleware {
	constructor(private cls: ClsService) {}

	use(req: Request, res: Response, next: NextFunction): void {
		const requestId = req.headers['x-request-id'] || randomUUID();
		this.cls.set('requestId', requestId);
		this.cls.set('userId', req.user?.id);

		res.setHeader('x-request-id', requestId);
		next();
	}
}

// Logger that includes request context
@Injectable()
export class ContextLogger {
	constructor(private cls: ClsService) {}

	log(message: string, data?: object): void {
		console.log(
			JSON.stringify({
				level: 'info',
				timestamp: new Date().toISOString(),
				requestId: this.cls.get('requestId'),
				userId: this.cls.get('userId'),
				message,
				...data
			})
		);
	}

	error(message: string, error: Error, data?: object): void {
		console.error(
			JSON.stringify({
				level: 'error',
				timestamp: new Date().toISOString(),
				requestId: this.cls.get('requestId'),
				userId: this.cls.get('userId'),
				message,
				error: error.message,
				stack: error.stack,
				...data
			})
		);
	}
}

// Pino integration for high-performance logging
import { LoggerModule } from 'nestjs-pino';

@Module({
	imports: [
		LoggerModule.forRoot({
			pinoHttp: {
				level: process.env.NODE_ENV === 'production' ? 'info' : 'debug',
				transport: process.env.NODE_ENV !== 'production' ? { target: 'pino-pretty' } : undefined,
				redact: ['req.headers.authorization', 'req.body.password'],
				serializers: {
					req: (req) => ({
						method: req.method,
						url: req.url,
						query: req.query
					}),
					res: (res) => ({
						statusCode: res.statusCode
					})
				}
			}
		})
	]
})
export class AppModule {}

// Usage with Pino
@Injectable()
export class UsersService {
	constructor(private logger: PinoLogger) {
		this.logger.setContext(UsersService.name);
	}

	async findOne(id: string): Promise<User> {
		this.logger.info({ userId: id }, 'Finding user');
		// Pino uses first arg for data, second for message
	}
}
```

Reference: [NestJS Logger](https://docs.nestjs.com/techniques/logger)
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall