Closed marty0678 closed 3 months ago
Looks like an issue has been opened with Electron Builder - https://github.com/electron-userland/electron-builder/issues/8175 and they have reported the same thing I have found, with pinning 24.13.0
.
External issue. Tested and works with electron-builder 24.13.3
What happened?
Setting up a brand new Quasar project following the instructions in the docs, will not allow Quasar to build an Electron app using builder. I've traced this issue to the 24.13.1 release of Electron Builder, 24.13.0 works correctly.
Only appears to affect pnpm - can not reproduce with yarn.
Release - https://github.com/electron-userland/electron-builder/releases/tag/v24.13.1 Suspect PR - https://github.com/electron-userland/electron-builder/pull/8052
What did you expect to happen?
To be able to install a fresh Quasar project with pnpm, switch to electron builder mode, and build the stock app.
Reproduction URL
https://github.com/marty0678/quasar-electron-builder-repro
How to reproduce?
Either reference the included repo and:
pnpm install
quasar build -m electron
Or just follow the steps below:
pnpm create quasar
pnpm install
if you didn't alreadyquasar.config.js
change theelectron
->bundler
frompackager
tobuilder
quasar dev -m electron
to verifyquasar build -m electron
to buildDuring the building stage of the package, you will get (shortened for brevity):
Flavour
Quasar CLI with Vite (@quasar/cli | @quasar/app-vite)
Areas
Quasar CLI Commands/Configuration (@quasar/cli | @quasar/app-webpack | @quasar/app-vite), Electron Mode
Platforms/Browsers
Electron
Quasar info output
Relevant log output
No response
Additional context
I don't believe this is a Quasar issue specifically, rather just needing to update the 'out of the box' experience to support Electron Builder's changes.
Note that reverting to electron-builder@24.13.0 fixes this or using yarn/npm also fixes this.
pnpm version - 9.0.6