Node.js

Node.js is a runtime that executes JavaScript outside the browser. In blockchain projects it can host APIs, prepare transactions, process events and connect internal services. It also provides an environment for development tools using the JavaScript and TypeScript ecosystem.

Not every Web3 component depends on Node.js. Foundry is written in Rust, as is Graph Node, even where JavaScript client tools or scripts are available. Identifying each component's runtime helps plan resources and maintenance without confusing development tooling with the services operated in production.

The event loop coordinates asynchronous work and supports network waits without blocking each request. This does not make every task parallel: intensive computation and long synchronous functions can prevent the main thread from serving other operations. Worker threads or separate processes can organise suitable CPU workloads.

RPC services need concurrency limits, timeouts and error handling. Retries depend on the operation: repeating a read and sending a payment again have different consequences. Configuration and recovery logic should preserve that distinction rather than apply one retry policy to all calls.

An indexer can retrieve block ranges, transform events and save a checkpoint. Its design covers duplicates, reorganisations and restart recovery. WebSocket subscriptions help detect activity, while historical reads close gaps after connection loss and provide a way to reconcile stored records.

For scheduled work, durable queues separate reception from execution. Operational records identify tasks and status without exposing keys or personal data. Measuring indexing lag, errors and queue size helps decide whether to increase capacity or revise the design instead of assuming that more processes will solve every bottleneck.

Node versions should follow runtime support and dependency compatibility. Pin versions across development, continuous integration and deployment, then test upgrades. Runtime TypeScript execution does not necessarily replace the project's separate type-checking step or validate external data entering the service.

Transaction-signing services should separate construction from authorisation and limit credential scope. A conventional account key does not become revocable merely because it is held in a secrets manager. Compromise response requires explicit account and permission design; the language does not solve that architecture on its own.