Skip to content

chore: 升级electron版本到41 #502

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Particaly wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: 升级electron版本到41 #502

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@
"@types/uuid": "^10.0.0",
"@vitejs/plugin-vue": "^6.0.1",
"concurrently": "^9.1.2",
"electron": "^38.1.2",
"electron": "^41.6.1",
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot May 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

由于本次升级跨度较大（38 -> 41），且 electron-builder.yml 中配置了 npmRebuild: false，请务必确认构建脚本中包含针对新版本 Electron ABI 重新编译原生模块（如 sharp、uiohook-napi 和 lmdb）的步骤。否则，打包后的应用在调用这些原生模块时会因 ABI 不兼容而崩溃。

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot May 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Electron 41.x 捆绑了 Node.js v24.x（如 pnpm-lock.yaml 所示）。目前 devDependencies 中的 @types/node 仍为 ^22.18.6（第 78 行）。这种版本不匹配可能会导致主进程代码在进行类型检查时无法识别 Node.js 24 的新特性，建议将 @types/node 同步升级到 ^24.x 以保持一致性。

"electron-builder": "^25.1.8",
"electron-vite": "^4.0.1",
"eslint": "^9.36.0",
Expand Down
63 changes: 51 additions & 12 deletions pnpm-lock.yaml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.