Skip to content

build(deps-dev): bump @electron-forge/plugin-vite from 8.0.0-alpha.10 to 8.0.1 - #2070

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/electron-forge/plugin-vite-8.0.1
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/electron-forge/plugin-vite-8.0.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

Bumps @electron-forge/plugin-vite from 8.0.0-alpha.10 to 8.0.1.

Release notes

Sourced from @​electron-forge/plugin-vite's releases.

v8.0.1

Electron Forge 8

It’s time for a new major version! Forge is now ESM-only on Node.js 22, the Vite plugin is out of experimental, create-electron-app owns project scaffolding, and Forge installs with far fewer dependencies.

Read the Breaking changes section before upgrading.

Highlights

  • ESM and Node.js 22. Every @electron-forge/* package is ESM-only and requires Node.js 22.17 or newer. Existing Forge configurations keep working in CommonJS or ESM projects. (#4059)
  • The Vite plugin is promoted to stable. @electron-forge/plugin-vite is no longer experimental and is covered by semver. It now targets Vite 8, builds each target in an isolated process, supports opt-in main-process hot restart (hotRestart: true) and honours a custom server.host. (#4382, #4167, #4163, #4226, #4346, #4363)
  • electron-forge publish is now electron-forge release to avoid conflict with the npm publish command. make always saves its results, so release --from-make can publish artifacts built by an earlier make, for example on another CI job. publish still works as a deprecated alias. (#4305, #4395)
  • One template per bundler. create-electron-app --template vite --typescript replaces the separate *-typescript templates. New projects use oxlint and oxfmt, moduleResolution: bundler and a release script, and init gains --package-manager and --electron-version flags. (#4229, #4186, #4175, #4107, #4037)
  • webpack output in your terminal. The webpack plugin renders compiler output as tabs in the terminal instead of a browser logger on port 9000. (#4389)
  • Lighter install. got, fs-extra, fast-glob, find-up, chalk, lodash, rechoir and others were replaced with Node.js built-ins. (#4189, #4250, #4227, #4248, #4245, #4066)
  • Makers and publishers. PKG notarization (#4234), MSIX outputFileName (#4295), typed copyright for deb and rpm (#4298), byte-level GitHub upload progress (#4304), and the artifact version in S3 and GCS keyResolver (#4033).

Breaking changes

Everyone

  • Node.js 22.17.0 or newer is required (was 16.4.0). (#4059)
  • All packages are ESM-only. The CLI needs no changes. If you call the programmatic API with require('@electron-forge/core'), that relies on Node's require(esm); switch to import to be safe. (#4059)
  • Custom makers, publishers, plugins and string packagerConfig hooks must have a default export (export default or module.exports =). (#4059)
  • Config templating was removed. Strings in your config are no longer rendered as lodash templates (${version}, ${year}, other package.json fields), and require:./path strings are no longer resolved. Use JavaScript in forge.config.* instead. (#4066)
  • Only forge.config.{js,mjs,cjs,ts,mts,cts} are loaded. Config files in other languages (CoffeeScript, Babel-registered files, etc.) are no longer supported through rechoir. (#4066)
  • init and import moved to create-electron-app. Use npx create-electron-app@latest my-app and npx create-electron-app@latest import. The electron-forge init and electron-forge import commands, and their core API functions, were removed. Importing Forge 5 projects (#4083) and loading globally installed templates (#4065) are no longer supported. (#4148)
  • init no longer guesses your package manager. It asks when run interactively and uses npm otherwise. Pass --package-manager pnpm, yarn or an exact version such as yarn@1.22.22 in scripts and CI. (#4107)
  • Deprecated, still working: publish → release, make --skip-package → --from-package, release --from-dry-run → --from-make, release --dry-run → make. Dry runs saved by Forge 7 cannot be resumed; run make again with Forge 8. (#4305, #4395)
  • Plugins are initialized once per command. make and release no longer re-resolve the config for their nested steps, so init() and resolveForgeConfig run once. (#4394)

Vite and webpack plugins

  • Main and preload bundles are emitted as .cjs. Both plugins stop with an error explaining the fix if your project still uses the old paths. (#4393)
    • Vite: set "main": ".vite/build/main.cjs" and load preloads with path.join(__dirname, 'preload.cjs').
    • webpack: set "main": ".webpack/main/index.cjs".
  • The Vite plugin targets Vite 8. Upgrade vite to 8.x and port custom Rollup options to Vite 8. (#4167)
  • The webpack loggerPort option was removed along with @electron-forge/web-multi-logger. In the terminal UI, press r to restart the app. (#4389)
  • webpack-dev-server 5. Custom devServer options must follow the v5 API. (#4308)

Makers

  • DMG output moved to out/make/dmg/<arch>/ (#4275) and PKG output moved to out/make/pkg/<arch>/ (#4383). Update any CI globs that upload from out/make/.
  • @electron-forge/maker-appx is deprecated and now builds .msix through electron-windows-msix. Several Desktop App Converter options are ignored with a warning, no development certificate is generated when devCert is unset, and a publisher is required. Move to @electron-forge/maker-msix. (#4392)
  • maker-deb rejects unsupported architectures, including arm (armel). Supported: ia32, x64, arm64, armv7l, mips64el. (#4059)
  • maker-wix only builds x64, ia64 and x86. (#3859)
  • maker-deb and maker-rpm use electron-installer-debian and electron-installer-redhat v4. (#4379)
  • Type renames: MakerFlatpakOptionsConfig is now MakerFlatpakConfigOptions, and maker-dmg no longer re-exports the electron-installer-dmg option types. (#4321)

Publishers

... (truncated)

Changelog

Sourced from @​electron-forge/plugin-vite's changelog.

Changelog

The changelog for subsequent updates is available for each release independently on this repo's GitHub Releases page. This document is preserved for historical purposes.

6.0.2 (2022-11-14)

6.0.1 (2022-11-08)

6.0.0 (2022-11-02)

6.0.0-beta.75 (2022-11-01)

New Features

6.0.0-beta.74 (2022-11-01)

Bug Fixes
  • do not proxify class instances in forge config (#3039) (a89ed7d3)
Other Changes
  • add proper package test for webpack ts template (#3040) (6e9cca35)

6.0.0-beta.73 (2022-11-01)

Bug Fixes

6.0.0-beta.72 (2022-10-31)

6.0.0-beta.71 (2022-10-31)

Bug Fixes
  • packager: "packaging application" log never stops when building for multiple architectures (#3006) (247f52ab)
  • publish: ignore unnecessary files when publishing to npm (#3024) (ab8ea661)
  • template-base: use minimum instead of exact version when replacing ELECTRON_FORGE/VERSION in templates (#3030) (7aaa7029)
  • use @​electron-forge/cli hint for project resolution (#3023) (b5d05874)
  • restore isProd in the webpack plugin (#3021) (531788ba)

6.0.0-beta.70 (2022-10-28)

Bug Fixes

... (truncated)

Commits
  • 48f38bb chore: bump version to 8.0.1 (#4426)
  • 40b4adf chore: bump version to 8.0.0 (#4425)
  • 1d268aa build(deps): bump vulnerable transitive and direct dependencies (#4408)
  • c012507 feat(bundlers)!: emit main and preload bundles as .cjs (#4393)
  • 29f5980 chore(deps)!: upgrade listr2 to v11 (#4375)
  • 5166ca9 feat(plugin-vite): graduate from experimental (#4382)
  • 99ef7be build(deps): bump @electron/* and electron-installer-* packages (#4379)
  • b52f517 feat(template)!: unify JS/TS templates (#4229)
  • f9c705d feat(plugin-vite): support custom server host in renderer dev server URL (#4363)
  • 1ccbd13 fix(typedoc): documentation & API completeness fixes (#4321)
  • Additional commits viewable in compare view

@dependabot
dependabot Bot requested review from a team and codebytere as code owners November 6, 2026 02:14
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Nov 6, 2026
@socket-security

socket-security Bot commented Nov 6, 2026 •

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updated@​electron-forge/​plugin-vite@​8.0.0-alpha.10 ⏵ 8.0.1100 +110091 +996100

View full report

@claude claude Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Nothing blocking. The comments below are optional suggestions. There is no need to push a fix for them before merging.

Comment thread yarn.lock
Comment on lines +528 to +534
"@electron-forge/plugin-vite@npm:8.0.1":
version: 8.0.1
resolution: "@electron-forge/plugin-vite@npm:8.0.1"
dependencies:
"@electron-forge/core-utils": "npm:8.0.0-alpha.10"
"@electron-forge/plugin-base": "npm:8.0.0-alpha.10"
"@electron-forge/shared-types": "npm:8.0.0-alpha.10"
"@electron-forge/core-utils": "npm:8.0.1"
"@electron-forge/plugin-base": "npm:8.0.1"
"@electron-forge/shared-types": "npm:8.0.1"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟣 pre-existing, not blocking: pre-existing: CI installs with yarn install --immutable will probably still fail. The lockfile has dangling references, and this bump adds one more. The new plugin-vite entry needs @ electron-forge/shared-types@ npm:8.0.1, but yarn.lock has no resolution block for that descriptor. Only the 8.0.0-alpha.10 block exists at yarn.lock:567. @ electron-forge/maker-base@ npm:8.0.1 is also missing. Fix: rerun yarn install so every referenced Forge 8.0.1 descriptor gets its own entry, then commit the complete lockfile.
A small fix can ride a push you are already making; otherwise a short reply is enough.

Why this was flagged

The new @ electron-forge/plugin-vite@ npm:8.0.1 entry at yarn.lock:528-539 depends on @ electron-forge/shared-types: npm:8.0.1 (yarn.lock:534). No "@ electron-forge/shared-types@ npm:8.0.1" block exists anywhere in yarn.lock; the only one is 8.0.0-alpha.10 at yarn.lock:567. @ electron-forge/maker-base@ npm:8.0.1 is referenced by maker-squirrel (yarn.lock:476) and has no entry either. CI and release run yarn install --immutable (.github/workflows/ci.yml:56, :138, release.yml:57, :127, :220). Yarn has to add the missing resolutions, and immutable mode rejects that, so the install step fails. The base lockfile already had the same gap through core-utils, plugin-base, plugin-fuses and maker-squirrel 8.0.1, so this is pre-existing. The PR says the lockfile was regenerated, yet it adds another dangling reference instead of fixing the gap.

Verification: Pre-existing. Trigger: yarn install --immutable, which CI runs at .github/workflows/ci.yml:56. The new block at yarn.lock:528-539 lists "@ electron-forge/shared-types": "npm:8.0.1". There is no shared-types@ npm:8.0.1 block. Yarn has to resolve these descriptors, which means rewriting the lockfile, and --immutable rejects that. The base lockfile (7aeea3b) was already broken the same way.

Bumps [@electron-forge/plugin-vite](https://github.com/electron/forge/tree/HEAD/packages/plugin/vite) from 8.0.0-alpha.10 to 8.0.1.
- [Release notes](https://github.com/electron/forge/releases)
- [Changelog](https://github.com/electron/forge/blob/main/CHANGELOG.md)
- [Commits](https://github.com/electron/forge/commits/v8.0.1/packages/plugin/vite)

---
updated-dependencies:
- dependency-name: "@electron-forge/plugin-vite"
  dependency-version: 8.0.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/electron-forge/plugin-vite-8.0.1 branch from f5c8947 to 1dead75 Compare November 6, 2026 03:40

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants