ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Languages & runtimes · #nodejs
When the glitch.json file is edited to change the start command, Glitch detects the modification and attempts to restart the application process. The goal is to ensure that the restarted process uses the updated command and loads any new or changed dependencies without stale code from the previous run. However, the live reload mechanism does not automaticall
Goal Determine the most reliable method for a Discord.js v14 bot to connect to the Discord gateway while minimizing latency and ensuring continued connectivity during Discord’s IP rotation. Constraints 1. The bot must maintain low connection latency, especially for high‑frequency message handling. 2. It should automatically adapt to Discord’s geo‑distributed
For a read-heavy endpoint returning large result sets from a Mongoose collection, the choice between .lean() and hydrated documents creates a direct tension between raw throughput and model-centric design. Hydrated documents preserve schema virtuals, getters, instance methods, and change tracking, but every result pays an instantiation cost that scales with
Node.js provides the process.env global object to manage environment variables, and recent versions include the --env-file flag for native loading of configuration files. This mechanism is commonly used to swap production credentials for test-specific secrets during integration testing. A challenge arises when asynchronous test suites attempt to mutate proce
I'm reviewing the network exposure defaults for a Node.js service built on the documented http.createServer().listen(port[, host]) API. My understanding is that omitting the host argument binds to all available IPv4 and IPv6 addresses ( 0.0.0.0 and :: ), which means a service can become reachable from external networks unless a firewall blocks it. I want to
http.Agent maintains a per-origin pool of keep-alive sockets. maxSockets caps concurrent sockets per origin and maxFreeSockets caps idle sockets retained, which together bound connection reuse under load. The global agent is shared across modules by default, so concurrent requests from different callers compete for the same limits. Keep-alive sockets remain
Integration boundary PM2's zero-downtime reload mechanism relies on sending SIGUSR2 to the master process, which then forwards SIGTERM to workers for graceful shutdown. The application must implement a SIGTERM handler that finishes in-flight requests before exiting. This contract sits at the boundary between PM2's process orchestration and the Node.js runtim
We plan to migrate a small non-monorepo Node.js application to pnpm in CI without interrupting deployments. The goal is to keep the existing npm-based pipeline running while a pnpm-lock.yaml is prepared, then switch to pnpm install once the lockfile is trusted. pnpm import can generate a pnpm-lock.yaml from an existing package-lock.json without modifying nod
Background FeathersJS v5 requires every service method to return a Promise. If a method returns a non‑promise value, the framework throws TypeError: Cannot read property 'then' of undefined . Under concurrent load, synchronous hooks can block the event loop, causing latency spikes that appear only when many requests pile up. Unresolved Decision While the doc
glitch
discordjs
mongoose
pm2
pnpm