javascript-strict

Never catch and swallow errors; always log with context using a format like [Module] identifier Action: message, then decide to retry, skip, or throw. Replace recursive retries with bounded loops using backoff, and throw after the retry limit is exhausted.

Use AbortController with a setTimeout that aborts the request, clearing the timer in a finally block. This replaces the older Promise.race timeout pattern and also supports caller-driven cancellation via an external signal.

Use const by default for anything never reassigned, let only when reassignment is required, and never use var. Destructure objects at declaration with defaults, for example const { mode = 'both', delay = 1000 } = options.

Yes, Node 22+ ships equivalents for many packages: global fetch replaces node-fetch, node:test replaces mocha or jest for simple libraries, --env-file replaces dotenv, fs.glob replaces glob, and node:sqlite covers simple database use.

Math.random is predictable and seedable, making it unsuitable for session IDs, password reset tokens, nonces, or salts. Use crypto.randomBytes from node:crypto instead, for example randomBytes(32).toString('hex') for a cryptographically random token.

Avoid writeFileSync in the event loop because it blocks execution for 5-50ms per call. Use await fs.promises.writeFile instead, and for large files or network data use streams with pipeline from node:stream/promises to handle backpressure.