code-reviewer-node

To review Express route handlers and middleware, apply Node.js-specific checks that target security vulnerabilities and performance bottlenecks in REST controllers, JWT/OAuth middleware, and TypeScript strict mode compliance.

Yes, you can review GraphQL resolvers and Apollo Server setup because the Node.js code review overlay explicitly targets these backend components alongside Express routes to ensure production-ready code quality.

The best way to review Bull or BullMQ job processors is layering Node-specific checks on top of a universal code reviewer to enforce TypeScript strict mode and Node.js version compatibility for queue processing files.

No, this overlay does not work with frontend React, Vue, or Angular code; it is designed exclusively for Node.js backend files like Express middleware and should not be triggered for frontend code.

You enforce TypeScript strict mode and Node.js version compatibility by running the Node.js-aware review rules that validate tsconfig settings and backend dependencies after applying universal code review standards.

Yes, you need to run a universal code reviewer first to establish baseline code quality, then apply this Node.js overlay to enforce backend-specific checks for Express security and Node.js compatibility.