Mongoose findByIdAndUpdate更新成功却返回错误的问题求助

Hey there! Let's break down your two issues one by one—they're probably not as tangled as they seem.

1. 为什么文档明明更新成功了，却还是报错？ #

First off, let's start with the most common quirk of Mongoose's findByIdAndUpdate method:

• It returns the old document by default: By default, findByIdAndUpdate sends back the pre-updated version of your document, not the fresh, updated one. If your code logic expects the new data (like passing it to the frontend or running post-update checks on it), this mismatch could easily trigger errors that feel unrelated to the actual update. Fix this by adding the returnDocument: 'after' option (for Mongoose 6+) or new: true (for older versions) to your update call.
• Misconfigured error handling: Double-check your database function's error-catching logic. Are you accidentally treating a valid (but old) document or null (only happens if the ID doesn't exist, which you said isn't the case here) as an error? For example, if you're using callbacks, make sure you're only throwing errors when the first callback parameter is truthy, not when the result document looks "unexpected".
• Missing validation triggers: Even if your request data fits your schema rules, findByIdAndUpdate doesn't run document-level validation by default. If your update relies on schema checks (like required fields or enum values), add { runValidators: true } to your options—otherwise, Mongoose might let invalid data slip into the database, and your code could throw errors later when processing the result.

Here's a corrected example of the update call:

const updatedUser = await User.findByIdAndUpdate(
  userId,
  updatePayload,
  { 
    returnDocument: 'after', // Fetch the updated document
    runValidators: true      // Enforce schema validation on updates
  }
);

2. Why am I still getting deprecation warnings even with res.status(status).send(body)? #

First, take a close look at the warning message—it should tell you exactly what's outdated. If you're sure your code uses the proper chained res.status().send() syntax, here are the likely culprits:

• Babel transpilation quirks: If your project uses Babel, old plugins or misconfigured presets might be translating your modern chained calls back to the deprecated res.send(status, body) format. Try temporarily disabling Babel (run your code directly without transpilation) to see if the warning disappears—if it does, you'll need to update your Babel config (like upgrading @babel/preset-env to a newer version).
• Third-party middleware or dependencies: The warning might not be coming from your code at all. Check if any middleware (like logging tools, error handlers, or authentication libraries) in your request chain is still using the old Express response syntax.
• Mongoose-specific deprecations: Sometimes warnings are tied to Mongoose, not Express. For example, older versions of Mongoose flag findByIdAndUpdate as deprecated in favor of findOneAndUpdate({ _id: id }, ...), or warn about using new: true instead of returnDocument: 'after'. Look for a Mongoose: prefix in the warning message to confirm this.

Quick Recap #

1. For the update success + error issue: Fix your findByIdAndUpdate options to return the new document and enable validation, then audit your error-handling logic for false positives.
2. For the deprecation warning: Pinpoint the warning's source (Express vs Mongoose), check for outdated code in dependencies, and verify if Babel is mangling your response calls.

内容的提问来源于stack exchange，提问作者Dmitry Klymenko