ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Languages & runtimes · #nodejs
PM2 Cluster Mode utilizes the Node.js cluster module to distribute incoming connections across multiple worker processes. When the instances property is set to max in an ecosystem file, PM2 spawns a process for every logical CPU core detected on the host machine. While this maximizes CPU utilization, each worker operates as a separate process with its own me
When a Puppeteer‑driven deployment fails, developers often turn to the DEBUG logging feature to see the internal Chrome DevTools Protocol messages that Puppeteer emits. However, DEBUG output does not include console.log statements or JavaScript errors generated by the page itself; those must be captured with separate page.on('console') and page.on('pageerror
The goal is to decide whether to rely on Node.js’ built‑in perf_hooks module or on external tracing solutions such as Chrome DevTools or OpenTelemetry for production bottleneck analysis. Constraints include keeping runtime overhead low, ensuring compatibility with Node.js v8.5.0+, capturing short‑lived event‑loop spikes, and integrating with existing observa
Nodemon vs Node.js Process: Duplicate Write Concerns Goal Determine how to configure Nodemon so that the Node.js application does not produce duplicate log entries when the process restarts immediately after a file change. Constraints Nodemon triggers a restart on every detected file event, and the underlying OS file‑watcher may emit multiple rapid events fo
Node.js HTTPS Agent keepAlive in Tests When running integration tests that hit an HTTPS endpoint without using production credentials, the default keepAlive setting on the https.Agent may influence both the number of TLS handshakes and the overall test duration. The Node.js documentation states that keepAlive defaults to false , but the actual behavior can v
When the CoffeeScript Node extension ( coffeescript/register ) is used, the compiler caches the generated JavaScript in Node's module cache so that subsequent require calls return the same compiled output. The goal is to determine whether the extension provides a mechanism to automatically refresh this cached JavaScript when the source .coffee file changes,
Recovery needs to recreate the working service and its required data after a machine or process is lost. Which artifacts and state need protection, and how should the restore be checked?
The same project needs to behave consistently on developer machines, in CI and after deployment. Which versions, dependencies and configuration should be recorded?
Node.js provides AsyncLocalStorage as a high-level API for maintaining state across asynchronous execution boundaries. This feature relies on the underlying async_hooks module to track the lifecycle of asynchronous resources via init, before, after, and destroy events. While this mechanism simplifies request-scoped context propagation, it introduces a known
pm2
puppeteer
coffeescript