Multer's default file size limit is unlimited, and that's not a typo
Node's most popular file upload middleware has no size cap unless you set one. A single request can fill your disk or your memory before you notice.
Node's most popular file upload middleware has no size cap unless you set one. A single request can fill your disk or your memory before you notice.
npm install prints peer dependency warnings and lets you proceed anyway. Most of the time that's fine. Sometimes it silently installs a version combination nobody has ever tested.
A scheduled job that fails without alerting anyone is worse than no job at all, because everyone assumes it's working. A dead man's switch catches what try/catch can't.
Node's fetch and most HTTP clients wait forever by default. One slow or dead dependency ties up your event loop and connection pool until nothing else can get through.
Sanitizing input stops an attacker from injecting a script tag. It doesn't stop an inline script that got through some other way from running. A Content-Security-Policy header does, and most AI-scaffolded apps never set one.
npm install doesn't just copy files. By default it executes any postinstall script a package defines, with your full user permissions, before you've opened a single file in that dependency.
Asking an AI assistant for an IAM policy so a Lambda can read from S3 often gets you Action: s3:* on Resource: *, a policy that works immediately and grants far more than the one bucket the function actually needs.
A database client that opens a fresh connection per request works fine in dev with one user clicking around. Under real traffic it silently exhausts the pool, and every request after that hangs until it times out.
Next.js inlines any environment variable prefixed NEXT_PUBLIC_ directly into the client JavaScript bundle at build time. Getting that prefix on a server-only secret doesn't cause an error, it just ships the secret to every visitor's browser.