n8n-conventions

n8n development conventions enforce TypeScript standards, error handling, frontend rules, backend structure, and testing patterns. Following these guidelines ensures consistency and adherence to established architectural principles when contributing to the n8n project.

To structure the n8n backend, use the Controller-Service-Repository pattern along with dependency injection. This architectural convention maintains separation of concerns and ensures scalable, maintainable code within the n8n ecosystem.

n8n testing conventions specify dedicated testing tools and essential pre-commit commands to validate code before submission. Running these checks ensures your TypeScript and frontend code adheres to the project's established quality standards.

Yes, n8n development requires specific TypeScript error handling patterns to maintain robustness. The conventions provide a quick reference for these critical rules, ensuring your code handles errors consistently across frontend and backend components.

Yes, this reference covers both frontend and backend n8n patterns. It outlines coding standards for TypeScript and frontend development, while also detailing backend structure conventions for comprehensive project adherence.

Following n8n coding standards ensures your contributions match the project's specific architectural principles and tooling. General TypeScript conventions may lack the required Controller-Service-Repository structure and error handling patterns established within the n8n ecosystem.