Electron 29.0.0 がリリースされました! It includes upgrades to Chromium 122.0.6261.39
, V8 12.2
, and Node.js 20.9.0
.
Electron チームは、Electron 29.0.0 のリリース発表にワクワクしています! npm install electron@latest
から npm でインストールするか、リリースウェブサイト からダウンロードできます。 このリリースの詳細は続きをご覧ください。
何かフィードバックがあれば、Twitter や Mastodon で共有したり、コミュニティの Discord に参加してみましょう! バグや機能の要望は Electron の Issue トラッカー で報告できます。
注目すべき変更
ハイライト
- Added a new top-level
webUtils
module, a renderer process module that provides a utility layer to interact with Web API objects. The first available API in the module iswebUtils.getPathForFile
. Electron's previousFile.path
augmentation was a deviation from web standards; this new API is more in line with current web standards behavior.
累積的変更
- Chromium
122.0.6261.39
- Chrome 122 と デベロッパーツール 122 の新機能
- Chrome 121 と デベロッパーツール 121 の新機能
- Node
20.9.0
- V8
12.2
Electron 29 upgrades Chromium from 120.0.6099.56
to 122.0.6261.39
, Node from 18.18.2
to 20.9.0
, and V8 from 12.0
to 12.2
.
新機能
- Added new
webUtils
module, a utility layer to interact with Web API objects, to replaceFile.path
augmentation. #38776 - Added net module to utility process. #40890
- Added a new Electron Fuse,
grantFileProtocolExtraPrivileges
, that opts thefile://
protocol into more secure and restrictive behaviour that matches Chromium. #40372 - Added an option in
protocol.registerSchemesAsPrivileged
to allow V8 code cache in custom schemes. #40544 - Migrated
app.{set|get}LoginItemSettings(settings)
to use Apple's new recommended underlying framework on macOS 13.0+. #37244
破壊的変更
Behavior Changed: ipcRenderer
can no longer be sent over the contextBridge
Attempting to send the entire ipcRenderer
module as an object over the contextBridge
will now result in
an empty object on the receiving side of the bridge. This change was made to remove / mitigate
a security footgun. You should not directly expose ipcRenderer or its methods over the bridge.
Instead, provide a safe wrapper like below:
contextBridge.exposeInMainWorld('app', {
onEvent: (cb) => ipcRenderer.on('foo', (e, ...args) => cb(args)),
});
Removed: renderer-process-crashed
event on app
The renderer-process-crashed
event on app
has been removed.
Use the new render-process-gone
event instead.
// Removed
app.on('renderer-process-crashed', (event, webContents, killed) => {
/* ... */
});
// Replace with
app.on('render-process-gone', (event, webContents, details) => {
/* ... */
});
Removed: crashed
event on WebContents
and <webview>
The crashed
events on WebContents
and <webview>
have been removed.
Use the new render-process-gone
event instead.
// Removed
win.webContents.on('crashed', (event, killed) => {
/* ... */
});
webview.addEventListener('crashed', (event) => {
/* ... */
});
// Replace with
win.webContents.on('render-process-gone', (event, details) => {
/* ... */
});
webview.addEventListener('render-process-gone', (event) => {
/* ... */
});
Removed: gpu-process-crashed
event on app
The gpu-process-crashed
event on app
has been removed.
Use the new child-process-gone
event instead.
// Removed
app.on('gpu-process-crashed', (event, killed) => {
/* ... */
});
// Replace with
app.on('child-process-gone', (event, details) => {
/* ... */
});
26.x.y サポートの終了
プロジェクトの サポートポリシー に則り、Electron 26.x.y はサポート終了を迎えました。 開発者とアプリケーションは新しいバージョンの Electron にアップグレードすることを推奨します。
E29 (Feb'24) | E30 (Apr'24) | E31 (Jun'24) |
---|---|---|
29.x.y | 30.x.y | 31.x.y |
28.x.y | 29.x.y | 30.x.y |
27.x.y | 28.x.y | 29.x.y |
次回予告
Did you know that Electron recently added a community Request for Comments (RFC) process? If you want to add a feature to the framework, RFCs can be a useful tool to start a dialogue with maintainers on its design. You can also see upcoming changes being discussed in the Pull Requests. To learn more, check out our Introducing electron/rfcs blog post, or check out the README of the electron/rfcs repository directly.
短期的には、Chromium、Node、V8 といった Electron を構成する主要コンポーネントの開発に遅れないでチームが注力し続けるでしょう。
Electron の公開タイムラインはこちらで ご覧いただけます。
今後の変更についての詳細は、予定されている破壊的変更 のページをご覧ください。