Meteor Accounts.createUser遇重复用户崩溃问题解决咨询

问题现象 #

• 服务端通过自定义Meteor方法调用Accounts.createUser，首次调用可正常创建用户；当用户已存在时，服务端try/catch块无法捕获错误，导致Meteor进程崩溃。
• 直接在客户端调用Accounts.createUser时，重复用户错误可通过回调正常接收，不会引发崩溃。

原始代码及错误信息 #

服务端方法代码 #

'test.createUser'(user) {
try {
  Accounts.createUser(
    {
      username: user.username,
      email: user.emails[0].address,
      profile: user.profile,
    },
  );
} catch (exception) {
  console.log('Error creating user:', exception);
  throw exception;
}

客户端调用代码 #

createUser() {
  Meteor.call(
    "test.createUser",
    {
      username: "myuser",
      emails: [{ address: "myuser@example.com", verified: true }],
      profile: {
        profile: "userProfile",
        name: "New User",
        path: null,
      },
    },
    (error) => {
      if (error) {
        console.error("Error:", error);
      }
    }
  );
}

服务端崩溃错误信息 #

W20241231-09:01:11.046(1)? (STDERR) meteor://💻app/packages/accounts-base.js:685
W20241231-09:01:11.046(1)? (STDERR)           const error = new Meteor.Error(errorCode, isErrorAmbiguous ? 'Something went wrong. Please check your credentials.' : msg);
W20241231-09:01:11.046(1)? (STDERR)                         ^
W20241231-09:01:11.067(1)? (STDERR) errorClass [Error]: Something went wrong. Please check your credentials. [403]
W20241231-09:01:11.067(1)? (STDERR)     at AccountsServer._handleError (packages/accounts-base/accounts_server.js:1523:19)
W20241231-09:01:11.068(1)? (STDERR)     at AccountsServer._checkForCaseInsensitiveDuplicates (packages/accounts-base/accounts_server.js:1491:14)
W20241231-09:01:11.068(1)? (STDERR)     at processTicksAndRejections (node:internal/process/task_queues:105:5)
W20241231-09:01:11.068(1)? (STDERR)     at AccountsServer._createUserCheckingDuplicates (packages/accounts-base/accounts_server.js:1504:5)
W20241231-09:01:11.068(1)? (STDERR)     at AccountsServer.createUser (packages/accounts-password/password_server.js:996:12) {
W20241231-09:01:11.068(1)? (STDERR)   isClientSafe: true,
W20241231-09:01:11.068(1)? (STDERR)   error: 403,
W20241231-09:01:11.068(1)? (STDERR)   reason: 'Something went wrong. Please check your credentials.',
W20241231-09:01:11.068(1)? (STDERR)   details: undefined,
W20241231-09:01:11.068(1)? (STDERR)   errorType: 'Meteor.Error'
W20241231-09:01:11.068(1)? (STDERR) }
W20241231-09:01:11.068(1)? (STDERR)
W20241231-09:01:11.068(1)? (STDERR) Node.js v22.11.0

客户端直接调用代码 #

createUser2() {
  const user = {
      username: "myuser",
      emails: [{ address: "myuser@example.com", verified: true }],
      password: "secret",
      profile: {
        profile: "userProfile",
        name: "New User",
        path: null,
      },
    },
  };
  try {
    Accounts.createUser(
      {
        username: user.username,
        email: user.emails[0].address,
        password: user.password,
        profile: user.profile,
      },
      (err) => {
        console.log("we got an error:", err);
      }
    );
  } catch (exception) {
    console.log("Error creating user:", exception);
    throw exception;
  }
}

客户端错误信息 #

we got an error:
{
"isClientSafe": true,
"error": 403,
"reason": "Something went wrong. Please check your credentials.",
"message": "Something went wrong. Please check your credentials. [403]",
"errorType": "Meteor.Error"
}

问题原因 #

服务端的Accounts.createUser在检测到重复用户时，抛出的是异步错误（错误栈中的processTicksAndRejections可证明）。普通try/catch仅能捕获同步执行的错误，无法拦截异步抛出的异常，因此会导致服务端进程崩溃。

解决方案 #

将服务端的Meteor方法改为异步函数，使用await调用Accounts.createUser，让异步错误能被try/catch正常捕获。

修改后的服务端方法代码 #

async 'test.createUser'(user) {
  try {
    // 使用await等待异步操作完成
    return await Accounts.createUser({
      username: user.username,
      email: user.emails[0].address,
      profile: user.profile,
    });
  } catch (exception) {
    console.log('Error creating user:', exception);
    // 将错误包装为Meteor.Error返回给客户端，避免进程崩溃
    throw new Meteor.Error(exception.error, exception.reason);
  }
}

说明 #

• async/await语法将异步操作转化为同步写法，使try/catch能够捕获异步错误。
• 捕获错误后，通过throw new Meteor.Error将错误安全传递给客户端，客户端的Meteor.call回调会收到错误信息，服务端不会再崩溃。

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