[Bug] failed to run server tests in node 20

[xiaotia3]

📦 部署环境

Other

📌 软件版本

main

💻 系统环境

Ubuntu

🌐 浏览器

Chrome

🐛 问题描述

failed to run server tests in node v20.18.1. but can run in bun v1.1.26 and node v18.16.0.

node -v
v20.18.1

npm run test-server:coverage

$ vitest run --config vitest.server.config.ts --coverage
The CJS build of Vite's Node API is deprecated. See https://vitejs.dev/guide/troubleshooting.html#vite-cjs-node-api-deprecated for more details.

 RUN  v1.2.2 /home/xiaotian/Repos/lobe-chat
      Coverage enabled with v8

 ❯ src/database/server/models/__tests__/message.test.ts (0)
 ❯ src/database/server/models/__tests__/topic.test.ts (0)
 ❯ src/database/server/models/__tests__/session.test.ts (0)
 ❯ src/database/server/models/__tests__/nextauth.test.ts (0)
 ❯ src/database/server/models/__tests__/file.test.ts (0)
 ❯ src/database/server/models/__tests__/chunk.test.ts (0)
 ❯ src/database/server/models/__tests__/knowledgeBase.test.ts (0)
 ❯ src/database/server/models/__tests__/user.test.ts (0)
 ❯ src/database/server/models/__tests__/agent.test.ts (0)
 ❯ src/database/server/models/__tests__/asyncTask.test.ts (0)
 ❯ src/database/server/models/__tests__/sessionGroup.test.ts (0)
 ❯ src/database/server/models/__tests__/plugin.test.ts (0)
 ❯ src/database/server/utils/idGenerator.test.ts (0)

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Suites 13 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

 FAIL  src/database/server/utils/idGenerator.test.ts [ src/database/server/utils/idGenerator.test.ts ]
 FAIL  src/database/server/models/__tests__/agent.test.ts [ src/database/server/models/__tests__/agent.test.ts ]
 FAIL  src/database/server/models/__tests__/asyncTask.test.ts [ src/database/server/models/__tests__/asyncTask.test.ts ]
 FAIL  src/database/server/models/__tests__/chunk.test.ts [ src/database/server/models/__tests__/chunk.test.ts ]
 FAIL  src/database/server/models/__tests__/file.test.ts [ src/database/server/models/__tests__/file.test.ts ]
 FAIL  src/database/server/models/__tests__/knowledgeBase.test.ts [ src/database/server/models/__tests__/knowledgeBase.test.ts ]
 FAIL  src/database/server/models/__tests__/message.test.ts [ src/database/server/models/__tests__/message.test.ts ]
 FAIL  src/database/server/models/__tests__/nextauth.test.ts [ src/database/server/models/__tests__/nextauth.test.ts ]
 FAIL  src/database/server/models/__tests__/plugin.test.ts [ src/database/server/models/__tests__/plugin.test.ts ]
 FAIL  src/database/server/models/__tests__/session.test.ts [ src/database/server/models/__tests__/session.test.ts ]
 FAIL  src/database/server/models/__tests__/sessionGroup.test.ts [ src/database/server/models/__tests__/sessionGroup.test.ts ]
 FAIL  src/database/server/models/__tests__/topic.test.ts [ src/database/server/models/__tests__/topic.test.ts ]
 FAIL  src/database/server/models/__tests__/user.test.ts [ src/database/server/models/__tests__/user.test.ts ]
TypeError: Cannot set property crypto of #<Object> which has only a getter
 ❯ tests/setup-db.ts:7:8
      5| dotenv.config();
      6|
      7| global.crypto = new Crypto();
       |        ^
      8|

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/13]⎯

 Test Files  13 failed (13)
      Tests  no tests
   Start at  16:56:01
   Duration  167ms (transform 14ms, setup 0ms, collect 0ms, tests 0ms, environment 0ms, prepare 37ms)

error: script "test-server:coverage" exited with code 1

if i replace code line 7 with following code, it works and no error message appears.

Object.defineProperty(global, 'crypto', {
  value: new Crypto(),
  writable: true,
});

📷 复现步骤

node -v
v20.18.1

npm run test-server:coverage

🚦 期望结果

No TypeError in setup-db.ts

📝 补充信息

No response

[lobehubbot]

👀 @xiaotia3

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

[dosubot[bot]]

@xiaotia3 你好! 我是 Dosu，我是一个可以帮助你解决 bug，回答问题，并成为贡献者的机器人。我会在等待人类维护者的过程中帮助你。

The issue you're encountering is due to changes in Node.js v20, where certain global properties, like crypto, are now read-only and cannot be directly reassigned. This is why you're seeing the error "Cannot set property crypto of # which has only a getter."

The workaround you found, using Object.defineProperty, is a valid solution. It allows you to define the crypto property on the global object without directly assigning it, which bypasses the restriction:

Object.defineProperty(global, 'crypto', {
  value: new Crypto(),
  writable: true,
});

This approach is effective because it uses Object.defineProperty to set the property, which is allowed even for read-only properties, as long as you don't attempt to change the property's configuration (like making it writable if it wasn't before). This should resolve the TypeError you're experiencing when running tests in Node.js v20.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[dosubot[bot]]

The issue you're encountering with the TypeError in setup-db.ts when running server tests on Node v20.18.1 is due to how Node.js handles global properties. In Node v20, directly assigning global.crypto = new Crypto(); may not properly define the crypto property on the global object, leading to the error.

By using Object.defineProperty(global, 'crypto', { value: new Crypto(), writable: true });, you explicitly define the property with specific attributes, ensuring it is writable and properly set up, which resolves the TypeError ^[1].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[arvinxx]

comment global.crypto = new Crypto(); and then rerun