ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Languages & runtimes · #nodejs
When running Node.js applications in PM2 cluster mode, the master process coordinates worker instances and receives telemetry such as logs and custom metrics via an internal IPC channel. The goal is to understand whether the volume of IPC messages generated by high-frequency logging or metric emission introduces measurable event-loop lag in the individual wo
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
Developers want Glitch projects to automatically respect the Node.js version range declared in the engines.node field of package.json, so that native modules built for a specific major version continue to work after a platform‑wide Node.js rollout. Currently Glitch provisions the latest default Node.js (v18) regardless of the declared range, shows the actual
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,
Event Loop Blocking in High-Throughput Flows Node-RED operates on a single-threaded Node.js event loop. When flows are configured to process high-frequency message bursts, the runtime may experience significant latency or reduced editor responsiveness. A specific concern arises when the Debug node is used to monitor large payloads or rapid message streams. B
Integration boundary Axios delegates all Node.js HTTP(S) connection handling to the built-in http.Agent (or https.Agent ). The agent’s maxSockets and keepAlive settings control how many concurrent connections are opened to a single host and whether sockets are reused across requests. Goal and constraints Developers running many simultaneous axios requests to
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?
Moving an HTTP client that relies on Node.js http.Agent keep-alive pooling across a Node.js major version boundary raises a configuration decision about socket limits. The affected feature is keep-alive socket reuse governed by maxSockets per origin and, in newer releases, maxTotalSockets for the default agent. agent.destroy() does not guarantee immediate cl
pm2
glitch
coffeescript
axios