Electron 29.0.0
Electron 29.0.0 wurde veröffentlicht! It includes upgrades to Chromium 122.0.6261.39, V8 12.2, and Node.js 20.9.0.
Das Electron-Team freut sich, die Veröffentlichung von Electron 29.0.0 ankündigen zu können! Sie können es mit npm über npm electron@latest installieren oder von unserer Releases-Website herunterladen. Lesen Sie weiter für Details zu dieser Version.
Wenn Sie Feedback haben, teilen Sie es uns bitte auf Twitter oder Mastodon mit oder treten Sie unserem Community-Discord bei! Bugs und Feature-Anfragen können im Issue-Tracker von Electron gemeldet werden.
Bemerkenswerte Änderungen
- Added a new top-level
webUtilsmodule, 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.pathaugmentation was a deviation from web standards; this new API is more in line with current web standards behavior.
Stack-Änderungen
- Chromium
122.0.6261.39- Neu in Chrome 122 und in DevTools 122
- Neu in Chrome 121 und in DevTools 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.
Neue Funktionen
- Added new
webUtilsmodule, a utility layer to interact with Web API objects, to replaceFile.pathaugmentation. #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.registerSchemesAsPrivilegedto 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
Breaking Changes
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) => {
/* ... */
});
Ende der Unterstützung für 26.x.y
Electron 26.x.y hat das Ende des Supports gemäß der Support-Richtlinie des Projekts erreicht. Developers and applications are encouraged to upgrade to a newer version of 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 |
What's Next
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.
In the short term, you can expect the team to continue to focus on keeping up with the development of the major components that make up Electron, including Chromium, Node, and V8.
Sie können die öffentliche Zeitleiste von Electron hier finden.
Weitere Informationen über zukünftige Änderungen können auf der Geplante Breaking Changes Seite gefunden werden.
