4 nodejs rules available
Browse optimized Kiro rules specifically designed for Node.js development. These rules help Kiro's AI understand Node.js best practices and patterns.
Node.js development spans from CLI tools to microservices, and AI rules should match your use case. Rules that specify your module system preference (ESM vs CommonJS), async patterns, and error handling conventions help generate production-ready Node.js code with proper dependency management.
When configuring Kiro for Node.js development, consider these recommendations:
Node.js rules cover module system preferences, async patterns, and production deployment considerations. Many include patterns for Express/Fastify servers, CLI tools with Commander or Yargs, and worker threads for CPU-intensive tasks.
For new projects, ESM is recommended and is the default in Node.js 18+. Use 'type': 'module' in package.json. For legacy projects or packages requiring broad compatibility, CommonJS rules may be more appropriate.
Many Node.js rules include TypeScript patterns with ts-node or tsx for development and proper build configurations for production. Look for 'typescript' tags for full TS coverage.
Yes, look for framework-specific rules tagged with 'express', 'fastify', 'nestjs', or 'hapi'. These include middleware patterns, request validation, and framework-specific conventions.
Generate SQS queue processing code
Kiro rules for AWS-native development with CDK, Lambda, and DynamoDB.
Generate S3 bucket operations
Generate DynamoDB access patterns
Create your own Kiro rules for Node.js and share with the community.