Node.js操作MongoDB如何区分多个唯一字段触发的11000错误

基于Node.js环境使用Mongoose操作MongoDB时，为用户模型的username、email两个字段配置了unique唯一约束。通过try/catch捕获数据库操作错误时，仅能通过err.code === 11000判断触发了唯一键重复错误，无法进一步区分重复错误来自username还是email字段，需要实现精准识别冲突字段、返回对应错误提示的逻辑。

附原有错误处理函数、用户模型代码：
原有错误处理逻辑：

const handleErrors = (err) => {
    let errors = { username: '', password: '', email: '', firstname: '', lastname: ''}
    if (err.code === 11000)
    {
        console.log(err);
        //check if username error or email error
    }
    if (err.message.includes('Users validation failed'))
    {
        Object.values(err.errors).forEach(({properties}) => {
            errors[properties.path] = properties.message;
        })
    }
    return errors;
}

原有用户模型代码：

// 注意：此处原代码存在笔误，开头少了字符c
onst mongoose = require('mongoose');
const bcrypt = require('bcrypt');
const { isEmail } = require('validator');

const userSchema = new mongoose.Schema({
    username: {
        type: String,
        required: [ true, "Username field can't be empty" ],
        minlength: [3, 'Username must be more than 3 characters'],
        maxlength: [20, 'Username must be less than 20 characters'],
        unique: true,
    },
    email: {
        type: String,
        required: [ true, "Email field can't be empty" ],
        maxlength: [50, 'Email must be less than 50 characters'],
        unique: true,
        validate: [isEmail, 'Please enter a valid email']
    },
    password: {
        type: String,
        required: [ true, "Password field can't be empty" ],
        minlength: [8, 'Password must be more than 3 characters'],
    },
    firstname: {
        type: String,
        required: [ true, "First name field can't be empty" ],
        minlength: [3, 'First name must be more than 3 characters'],
        maxlength: [20, 'First name must be less than 20 characters'],
    },
    lastname: {
        type: String,
        required: [ true, "Last name field can't be empty" ],
        minlength: [3, 'Last name must be more than 3 characters'],
        maxlength: [20, 'Last name must be less than 20 characters'],
    },
    points: {
        type: String,
        default: "0",
    },
})

userSchema.pre('save', async function (next) {
    const salt = await bcrypt.genSalt();
    this.password = await bcrypt.hash(this.password, salt);
    next();
});

module.exports = mongoose.model('Users', userSchema);

Mongoose抛出11000唯一键重复错误时，错误对象自带err.keyValue属性，存储了所有触发唯一约束冲突的字段名和对应重复值，直接解析该属性即可精准定位冲突字段，无需复杂正则匹配错误信息。

修改后的错误处理函数如下：

const handleErrors = (err) => {
    let errors = { username: '', password: '', email: '', firstname: '', lastname: ''}
    if (err.code === 11000)
    {
        // 遍历所有冲突字段
        Object.keys(err.keyValue).forEach(conflictField => {
            // 仅处理预定义的表单字段，避免其他唯一键冲突污染返回结果
            if (Object.prototype.hasOwnProperty.call(errors, conflictField)) {
                // 按字段返回自定义提示
                switch(conflictField) {
                    case 'username':
                        errors[conflictField] = '用户名已被注册，请更换用户名';
                        break;
                    case 'email':
                        errors[conflictField] = '邮箱已被注册，请更换邮箱或直接登录';
                        break;
                    default:
                        errors[conflictField] = `${conflictField}已存在，请更换后重试`
                }
            }
        })

        // Mongoose 5及更早版本无keyValue属性时，使用正则兜底解析
        if (Object.keys(err.keyValue).length === 0 && err.errmsg) {
            const fieldMatch = err.errmsg.match(/index:\s+.*?\.\$([^\s]+)_1\s+dup key/);
            if (fieldMatch && Object.prototype.hasOwnProperty.call(errors, fieldMatch[1])) {
                errors[fieldMatch[1]] = fieldMatch[1] === 'username' ? '用户名已被注册，请更换用户名' : '邮箱已被注册，请更换邮箱或直接登录';
            }
        }
    }
    if (err.message.includes('Users validation failed'))
    {
        Object.values(err.errors).forEach(({properties}) => {
            errors[properties.path] = properties.message;
        })
    }
    return errors;
}

• 先修正用户模型文件的语法笔误：文件开头的onst mongoose改为const mongoose，否则代码会直接抛出语法错误无法运行
• unique: true是MongoDB层面的索引约束，不属于Mongoose Schema内置校验规则，因此唯一键冲突错误不会进入Users validation failed的校验分支，必须单独处理11000错误码
• 开发阶段如果修改过Schema的唯一字段配置，需要手动删除本地旧集合、或调用Users.syncIndexes()同步数据库索引，否则旧索引残留会导致冲突字段识别异常
• 生产环境建议提前在数据库层面创建好对应唯一索引，避免服务启动时自动建索引带来的性能风险

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