Electron 34.0.0
Electron 34.0.0 がリリースされました! It includes upgrades to Chromium 132.0.6834.83, V8 13.2, and Node 20.18.1.
Electron チームは、Electron 34.0.0 のリリース発表にワクワクしています! npm install electron@latest
から npm でインストールするか、リリースウェブサイト からダウンロードできます。 このリリースの詳細は続きをご覧ください。
If you have any feedback, please share it with us on Bluesky or Mastodon, or join our community Discord! バグや機能の要望は Electron の Issue トラッカー で報告できます。
注目すべき変更
HTTP Compression Shared Dictionary Management APIs
HTTP compression allows data to be compressed by a web server before being received by the browser. Modern versions of Chromium support Brotli and Zstandard, which are newer compression algorithms that perform better for text files than older schemes such as gzip.
Custom shared dictionaries further improve the efficiency of Brotli and Zstandard compression. See the Chrome for Developers blog on shared dictionaries for more information.
@felixrieseberg added the following APIs in #44950 to manage shared dictionaries at the Session level:
session.getSharedDictionaryUsageInfo()
session.getSharedDictionaryInfo(options)
session.clearSharedDictionaryCache()
session.clearSharedDictionaryCacheForIsolationKey(options)
Unresponsive Renderer JavaScript Call Stacks
Electron's unresponsive
event occurs whenever a renderer process hangs for an excessive period of time. The new WebFrameMain.collectJavaScriptCallStack()
API added by @samuelmaddock in #44204 allows you to collect the JavaScript call stack from the associated WebFrameMain
object (webContnets.mainFrame
).
This API can be useful to determine why the frame is unresponsive in cases where there's long-running JavaScript events causing the process to hang. For more information, see the proposed web standard Crash Reporting API.
const { app } = require('electron');
app.commandLine.appendSwitch(
'enable-features',
'DocumentPolicyIncludeJSCallStacksInCrashReports',
);
app.on('web-contents-created', (_, webContents) => {
webContents.on('unresponsive', async () => {
// Interrupt execution and collect call stack from unresponsive renderer
const callStack = await webContents.mainFrame.collectJavaScriptCallStack();
console.log('Renderer unresponsive\n', callStack);
});
});
This API requires the 'Document-Policy': 'include-js-call-stacks-in-crash-reports'
header to be enabled. See #45356 for more details.
累積的変更
- Chromium
132.0.6834.83
- Node
20.18.1
- V8
13.2
Electron 34 では、130.0.6723.44
から 132.0.6834.83
へ、Node は 20.18.2
から 20.18.1
へ、V8 は 13.0
から 13.2
へとアップグレードしています。
新機能
- Added APIs to manage shared dictionaries for compression efficiency using Brotli or ZStandard. The new APIs are
session.getSharedDictionaryUsageInfo()
,session.getSharedDictionaryInfo(options)
,session.clearSharedDictionaryCache()
, andsession.clearSharedDictionaryCacheForIsolationKey(options)
. #44950 - Added
WebFrameMain.collectJavaScriptCallStack()
for accessing the JavaScript call stack of unresponsive renderers. #44938 - Added
WebFrameMain.detached
for frames in an unloading state.- Added
WebFrameMain.isDestroyed()
to determine if a frame has been destroyed. - Fixed
webFrameMain.fromId(processId, frameId)
returning aWebFrameMain
instance which doesn't match the given parameters when the frame is unloading. #43473
- Added
- Added error event in utility process to support diagnostic reports on V8 fatal errors. #43774
- Feat: GPU accelerated shared texture offscreen rendering. #42953
破壊的変更
Behavior Changed: menu bar will be hidden during fullscreen on Windows
This brings the behavior to parity with Linux. Prior behavior: Menu bar is still visible during fullscreen on Windows. New behavior: Menu bar is hidden during fullscreen on Windows.
Correction: This was previously listed as a breaking change in Electron 33, but was first released in Electron 34.
31.x.y サポートの終了
プロジェクトの サポートポリシー に則り、Electron 31.x.y はサポート終了を迎えました。 開発者とアプリケーションは新しいバージョンの Electron にアップグレードすることを推奨します。
E34 (2025 年 1 月) | E35 (Apr'25) | E36 (Jun'25) |
---|---|---|
34.x.y | 35.x.y | 36.x.y |
33.x.y | 34.x.y | 35.x.y |
32.x.y | 33.x.y | 34.x.y |
次回予告
短期的には、Chromium、Node、V8 といった Electron を構成する主要コンポーネントの開発に遅れないでチームが注力し続けるでしょう。
Electron の公開タイムラインはこちらで ご覧いただけます。
今後の変更についての詳細は、予定されている破壊的変更 のページをご覧ください。