chore(deps): bump the production-dependencies group across 1 directory with 4 updates

[dependabot]

Bumps the production-dependencies group with 4 updates in the / directory: electron-to-chromium, esbuild, electron and electron-nightly.

Updates electron-to-chromium from 1.5.336 to 1.5.340

Commits

• 6d2cfbd 1.5.340
• d02552a generate new version
• ce4abfa 1.5.339
• 059f457 generate new version
• e54c94b 1.5.338
• fad2989 generate new version
• b09b91e 1.5.337
• a12c226 generate new version
• See full diff in compare view

Updates esbuild from 0.27.7 to 0.28.0

Release notes

Sourced from esbuild's releases.

v0.28.0

• Add support for with { type: 'text' } imports (#4435)

  The import text proposal has reached stage 3 in the TC39 process, which means that it's recommended for implementation. It has also already been implemented by Deno and Bun. So with this release, esbuild also adds support for it. This behaves exactly the same as esbuild's existing text loader. Here's an example:

  import string from './example.txt' with { type: 'text' }
  console.log(string)

• Add integrity checks to fallback download path (#4343)

  Installing esbuild via npm is somewhat complicated with several different edge cases (see esbuild's documentation for details). If the regular installation of esbuild's platform-specific package fails, esbuild's install script attempts to download the platform-specific package itself (first with the npm command, and then with a HTTP request to registry.npmjs.org as a last resort).

  This last resort path previously didn't have any integrity checks. With this release, esbuild will now verify that the hash of the downloaded binary matches the expected hash for the current release. This means the hashes for all of esbuild's platform-specific binary packages will now be embedded in the top-level esbuild package. Hopefully this should work without any problems. But just in case, this change is being done as a breaking change release.

• Update the Go compiler from 1.25.7 to 1.26.1

  This upgrade should not affect anything. However, there have been some significant internal changes to the Go compiler, so esbuild could potentially behave differently in certain edge cases:

  • It now uses the new garbage collector that comes with Go 1.26.
  • The Go compiler is now more aggressive with allocating memory on the stack.
  • The executable format that the Go linker uses has undergone several changes.
  • The WebAssembly build now unconditionally makes use of the sign extension and non-trapping floating-point to integer conversion instructions.

  You can read the Go 1.26 release notes for more information.

Changelog

Sourced from esbuild's changelog.

0.28.0

• Add support for with { type: 'text' } imports (#4435)

  The import text proposal has reached stage 3 in the TC39 process, which means that it's recommended for implementation. It has also already been implemented by Deno and Bun. So with this release, esbuild also adds support for it. This behaves exactly the same as esbuild's existing text loader. Here's an example:

  import string from './example.txt' with { type: 'text' }
  console.log(string)

• Add integrity checks to fallback download path (#4343)

  Installing esbuild via npm is somewhat complicated with several different edge cases (see esbuild's documentation for details). If the regular installation of esbuild's platform-specific package fails, esbuild's install script attempts to download the platform-specific package itself (first with the npm command, and then with a HTTP request to registry.npmjs.org as a last resort).

  This last resort path previously didn't have any integrity checks. With this release, esbuild will now verify that the hash of the downloaded binary matches the expected hash for the current release. This means the hashes for all of esbuild's platform-specific binary packages will now be embedded in the top-level esbuild package. Hopefully this should work without any problems. But just in case, this change is being done as a breaking change release.

• Update the Go compiler from 1.25.7 to 1.26.1

  This upgrade should not affect anything. However, there have been some significant internal changes to the Go compiler, so esbuild could potentially behave differently in certain edge cases:

  • It now uses the new garbage collector that comes with Go 1.26.
  • The Go compiler is now more aggressive with allocating memory on the stack.
  • The executable format that the Go linker uses has undergone several changes.
  • The WebAssembly build now unconditionally makes use of the sign extension and non-trapping floating-point to integer conversion instructions.

  You can read the Go 1.26 release notes for more information.

Commits

• 6a794df publish 0.28.0 to npm
• 64ee0ea fix #4435: support with { type: text } imports
• ef65aee fix sort order in snapshots_packagejson.txt
• 1a26a8e try to fix test-old-ts, also shuffle CI tasks
• 556ce6c use '' instead of null to omit build hashes
• 8e675a8 ci: allow missing binary hashes for tests
• 7067763 Reapply "update go 1.25.7 => 1.26.1"
• 39473a9 fix #4343: integrity check for binary download
• See full diff in compare view

Updates electron from 41.2.0 to 41.2.1

Release notes

Sourced from electron's releases.

electron v41.2.1

Release Notes for v41.2.1

Fixes

• Added missing metadata fields to contentTracing traces. #51021 (Also in 42)
• Changed the kResizeThreshold to trigger the resize on corners. #51002 (Also in 42)
• Fixed fs.stat on files inside asar archives returning undefined for blksize and blocks instead of numeric values. #50876 (Also in 40, 42)
• Fixed a crash when rendering PDFs when Site Isolation is disabled. #50845 (Also in 42)
• Fixed a memory leak where Menu items were not cleaned up after Menu.setApplicationMenu was called repeatedly. #50830 (Also in 40, 42)
• Fixed an issue where DevTools would re-attach to the window when opened after previously being detached. #50816 (Also in 39, 40, 42)
• Fixed an issue where setSimpleFullScreen on macOS would exit when web content called requestFullscreen(). #50985 (Also in 40, 42)
• Fixed an issue where closing devtools immediately after focus caused a crash. #51037 (Also in 42)
• Fixed an issue where webContents.print() would ignore pageSize / mediaSize when silent was true. #50856 (Also in 42)
• Fixed aspect ratio min/max size clamping to correctly account for extraSize on macOS. #50835 (Also in 40, 42)
• Fixed crash when app.setPath('sessionData') was called with a non-existent directory. #50958 (Also in 42)
• Fixed resize hit targets for frameless windows on Windows. Resize targets now start at the side and bottom edges of the window and extend outward when frame: false, matching the behavior for windows with frames. #50863 (Also in 42)
• Fixed the crash keys being lost and the crash reporter hanging on macOS when many dynamic crash keys were registered. #50837 (Also in 40, 42)
• Moved Electron-specific help menu links to the default app only; unpackaged apps will no longer see these items in their default menu. #50859 (Also in 40, 42)

Other Changes

• Backported fix for none. #50880
• Backported upstream fixes for two edge cases in the WebNN TFLite graph builder. #50983
• Backported upstream v8 fixes for a maglev use-count accounting issue and an inspector InspectedContext lifetime issue. #50991
• Updated Chromium to 146.0.7680.188. #50787
• Updated Node.js to v24.14.1. #50478

Commits

• 8ee008a fix: simpleFullScreen exits when web content calls requestFullscreen (#50...
• 881d198 fix: avoid window drag during corner resize in MAS build (#51002)
• af412f8 test: add desktopCapturer icon validation (#50821)
• 290d3cf test: fixup autoupdater tests failures (#51059)
• 04f4d4b chore: backport cppgc cleanups (#50915)
• a8c34b8 build: authenticate sudowoodo /token exchange via Actions OIDC (41-x-y) (#51053)
• ec9b4dc fix: crash when closing devtools after focus (#51037)
• 7ffb676 ci: split macos-x64 tests into 3 shards (41-x-y) (#50974)
• 0d41720 fix: include missing metadata in trace files (#51021)
• b610b41 ci: capture fatal errors in clang problem matcher (#50997)
• Additional commits viewable in compare view

Updates electron-nightly from 43.0.0-nightly.20260415 to 43.0.0-nightly.20260416

Commits

• 99e8170 fix: fix types in devtools console for release (#51104)
• 02d90a5 chore: add Node.js skill to settings (#51092)
• 3c826c7 fix: linter issue (#51105)
• f35122b test: add tab source ID tests for media handler (#51068)
• 5523130 ci: build a patched siso for Windows builds (#51077)
• abffba4 fix: use CreateDataProperty when copying objects across contextBridge (#50900)
• d164b7a fix: prevent uaf when destroying guest WebContents during event emission (#50...
• 2434c5a fix: show 'Electron Isolated Context' in Dev Tools (#51062)
• cc738f2 refactor: avoid unnecessary extends EventEmitter in lib (#51058)
• 9569c48 refactor: SafeStorage never emits, so do not inherit from EventEmitter (#51057)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.