You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i am trying to build from the git as i noticed the releases are quite old. after cloning i used pnpm install as i noticed the pnpm lock file. but after installing using pnpm install when i try to build the package either with pnpm package or make i get this error from electron-forge.
> [email protected] package /home/silver/game/debugtron
> electron-forge package
✖ Checking your system
An unhandled error has occurred inside Forge:
Command failed with a non-zero return code (1):
yarn --version
Usage Error: This project is configured to use pnpm
$ yarn ...
Error: Command failed with a non-zero return code (1):
yarn --version
Usage Error: This project is configured to use pnpm
$ yarn ...
at ChildProcess.<anonymous> (/home/silver/game/debugtron/node_modules/.pnpm/@[email protected]/node_modules/@malept/cross-spawn-promise/dist/src/index.js:101:24)
at ChildProcess.emit (node:events:527:28)
at maybeClose (node:internal/child_process:1090:16)
at ChildProcess._handle.onexit (node:internal/child_process:302:5)
ELIFECYCLE Command failed with exit code 1.
so i am wondering do i have to install with yarn first then run pnpm or am i missing something?
The text was updated successfully, but these errors were encountered:
You can safely remove it. It's experimental field and defines what package manager is expected to be used.
Unfortunately it seems electron-forge is checking yarn version and this line causes error.
i am trying to build from the git as i noticed the releases are quite old. after cloning i used pnpm install as i noticed the pnpm lock file. but after installing using pnpm install when i try to build the package either with pnpm package or make i get this error from electron-forge.
so i am wondering do i have to install with yarn first then run pnpm or am i missing something?
The text was updated successfully, but these errors were encountered: