ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #express
Goal: Ensure that adding concurrent requests does not increase the latency introduced by CPU‑bound middleware in an Express application. Constraint: Express executes each middleware synchronously on the Node.js event loop, and the framework does not provide a built‑in mechanism to offload such work to worker threads or to defer it automatically. Developers m
We run a small Express application that authenticates users with Passport's local strategy backed by server-side sessions (connect-mongo). The plan is to move to an OAuth2 authorization-code flow without forcing any user to log out mid-migration, and I need to commit to one of two documented approaches before writing code. Approach A is incremental: keep the
Kraken.js and Lusca at the middleware boundary Kraken.js wires Lusca's security modules declaratively through the lusca key in config.json , rather than through imperative app.use() calls. My goal is to enable Lusca's CSRF protection in a Kraken app while keeping the guarantee that the session middleware it depends on is registered before Lusca in the middle
Goal Implement safe query bounding and pagination for a REST endpoint that serves large datasets, ensuring that malicious or accidental oversized requests cannot exhaust memory or degrade database performance. Constraints and uncertainty Express parses query strings into req.query using the built‑in qs parser (default since Express 4.16) but does not enforce
NestJS 10 changed the default HTTP server from Express to Fastify, creating an integration boundary for teams that maintain Express-style middleware across version 9 and version 10 codebases. The precise goal is to determine which existing Express middleware patterns remain viable under the Fastify runtime without introducing runtime failures or hidden behav
Goal Determine whether an Express application that sets app.set('trust proxy', true) automatically treats all cookies as secure when the request arrives over HTTPS via a reverse proxy, even if the cookie options omit secure:true . Context When trust proxy is enabled, Express marks req.secure true if the X-Forwarded-Proto header equals https . The cookieParse
Kraken.js configuration and duplicate writes I have a Kraken.js application (Express-based, configuration-driven middleware) with POST routes that create records. Clients and an upstream proxy can legitimately retry requests, and Kraken itself does not document any built-in retry or idempotency handling, so a repeated POST can reach the same route handler tw
This seems like such a simple question to answer, but finding an answer for this seems impossible. I am building a password reset feature for a backend application with Express and Typescript. I am using Postgres for the database and Typeorm for data manipulation. I have a User entity with these two columns in my database: @Column({ unique: true, nullable: t
The objective is to restart a small Express application without any request loss, preserving active connections and session state. The built‑in cluster module creates multiple worker processes that share the same port, allowing a graceful restart of one worker while others continue serving traffic, but requires manual load‑balancing configuration. PM2’s relo
passport
krakenjs
nestjs
fastify
typescript