javascript-stack

Keep each module focused on a single responsibility with explicit inputs and outputs. Follow the repo's existing module format and build setup, and avoid clever dynamic patterns that obscure dependencies between modules.

Use consistent async patterns such as async/await with try/catch blocks, and handle errors explicitly rather than letting them propagate silently. Consistency across the codebase matters more than any single pattern choice.

Validate data at system boundaries where runtime types matter, such as API endpoints, message consumers, and file parsers. Internal code can then trust the data instead of re-checking assumptions everywhere.

JavaScript's dynamic typing means type mismatches and undefined values surface only when code executes. Weak input handling and implicit assumptions amplify this, so boundary validation and predictable patterns reduce runtime-only failures.

Avoid dynamic patterns like runtime property injection or metaprogramming when a straightforward static approach works. Predictable behavior is easier to debug, lint, and review than clever dynamic constructs.