- I have read the contribution documentation for this project.
- I agree to follow the code of conduct that this project follows, as appropriate.
- I have searched the issue tracker for an issue that matches the one I want to file, without success.
Please describe your issue:
I installed electron-forge using npm install -g electron-forge, but when I run this electron-forge init rand I got the following in the log.
Console output when you run electron-forge with the environment variable DEBUG=electron-forge:*. (Instructions on how to do so here). Please include the stack trace if one exists.
An unhandled error has occurred inside Forge:
Failed to install modules: ["eslint@^3","eslint-config-airbnb@^15","eslint-plugin-import@^2","eslint-plugin-jsx-a11y@^5","eslint-plugin-react@^7"]
With output: Exited with status 4294963248
Error: Failed to install modules: ["eslint@^3","eslint-config-airbnb@^15","eslint-plugin-import@^2","eslint-plugin-jsx-a11y@^5","eslint-plugin-react@^7"]
With output: Exited with status 4294963248
at C:UsersUserAppDataRoamingnpmnode_moduleselectron-forgedistutilinstall-dependencies.js:55:13
at Generator.throw (<anonymous>)
at Generator.tryCatcher (C:UsersUserAppDataRoamingnpmnode_moduleselectron-forgenode_modulesbluebirdjsreleaseutil.js:16:23)
at PromiseSpawn._promiseRejected (C:UsersUserAppDataRoamingnpmnode_moduleselectron-forgenode_modulesbluebirdjsreleasegenerators.js:107:10)
at Promise._settlePromise (C:UsersUserAppDataRoamingnpmnode_moduleselectron-forgenode_modulesbluebirdjsreleasepromise.js:576:26)
at Promise._settlePromise0 (C:UsersUserAppDataRoamingnpmnode_moduleselectron-forgenode_modulesbluebirdjsreleasepromise.js:614:10)
at Promise._settlePromises (C:UsersUserAppDataRoamingnpmnode_moduleselectron-forgenode_modulesbluebirdjsreleasepromise.js:689:18)
at Async._drainQueue (C:UsersUserAppDataRoamingnpmnode_moduleselectron-forgenode_modulesbluebirdjsreleaseasync.js:133:16)
at Async._drainQueues (C:UsersUserAppDataRoamingnpmnode_moduleselectron-forgenode_modulesbluebirdjsreleaseasync.js:143:10)
at Immediate.Async.drainQueues (C:UsersUserAppDataRoamingnpmnode_moduleselectron-forgenode_modulesbluebirdjsreleaseasync.js:17:14)
at runCallback (timers.js:789:20)
at tryOnImmediate (timers.js:751:5)
at processImmediate [as _immediateCallback] (timers.js:722:5)
**What command line arguments are you passing?**
What does your config.forge data in package.json look like?
I just let the command create that for me
Please provide either a failing minimal testcase (with a link to the code) or detailed steps to
reproduce your problem. Using electron-forge init is a good starting point, if that is not the
source of your problem.
I used to have a working program but abandoned the project and am now coming back to it. I tried running it and it was saying errors. Here is my code:
const { app, BrowserWindow } = require(‘electron’);
const path = require(‘path’);
if (require(‘electron-squirrel-startup’)) {
app.quit();
}
const createWindow = () => {
const mainWindow = new BrowserWindow({
width: 1500,
height: 900,
resizable: false,
fullscreen: false,
frame: false,
fullscreenable: false,
});
mainWindow.loadFile(path.join(__dirname, ‘home.html’));
mainWindow.setIcon(‘./Assets/Main.png’, ‘Icon’)
mainWindow.setMenuBarVisibility(false)
};
app.on(‘ready’, createWindow);
app.on(‘window-all-closed’, () => {
if (process.platform !== ‘darwin’) {
app.quit();
}
});
app.on(‘activate’, () => {
if (BrowserWindow.getAllWindows().length === 0) {
createWindow();
}
});
This is my error:
C:UsersLiamDocumentsBotsCloud Botsrcindex.js:27
app.whenReady().then(createWindow)
^
TypeError: Cannot read property ‘whenReady’ of undefined
at Object.<anonymous> (C:UsersLiamDocumentsBotsCloud Botsrcindex.js:27:5)
at Module._compile (internal/modules/cjs/loader.js:1063:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
at Module.load (internal/modules/cjs/loader.js:928:32)
at Function.Module._load (internal/modules/cjs/loader.js:769:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
at internal/main/run_main_module.js:17:47
I started learning on the electron by using the GitHub on demand training. When I executed the below command. The system throws the error.
electron % electron-forge init electron-app
⚠ Could not check Yarn version "0.32
", assuming incompatible
⚠ You are using Yarn, but not a known good version.
The known versions that work with Electron Forge are: 0.23.3 || 0.24.6 || >= 1.0.0 || 0.27.5
✔ Checking your system
? WARNING: The specified path: "/home/anoobbava/electron/electron-app" is not empty, do you wish to continue? Yes
✔ Initializing Project Directory
✔ Initializing Git Repository
✔ Copying Starter Files
✔ Initializing NPM Module
✖ Installing NPM Dependencies
An unhandled error has occurred inside Forge:
Failed to install modules: ["electron-compile","electron-squirrel-startup"]
With output: Exited with status 1
Error: Failed to install modules: ["electron-compile","electron-squirrel-startup"]
With output: Exited with status 1
at /home/anoobbava/.nvm/versions/node/v9.9.0/lib/node_modules/electron-forge/dist/util/install-dependencies.js:55:13
at Generator.throw (<anonymous>)
at Generator.tryCatcher (/home/anoobbava/.nvm/versions/node/v9.9.0/lib/node_modules/electron-forge/node_modules/bluebird/js/release/util.js:16:23)
at PromiseSpawn._promiseRejected (/home/anoobbava/.nvm/versions/node/v9.9.0/lib/node_modules/electron-forge/node_modules/bluebird/js/release/generators.js:107:10)
at Promise._settlePromise (/home/anoobbava/.nvm/versions/node/v9.9.0/lib/node_modules/electron-forge/node_modules/bluebird/js/release/promise.js:576:26)
at Promise._settlePromise0 (/home/anoobbava/.nvm/versions/node/v9.9.0/lib/node_modules/electron-forge/node_modules/bluebird/js/release/promise.js:614:10)
at Promise._settlePromises (/home/anoobbava/.nvm/versions/node/v9.9.0/lib/node_modules/electron-forge/node_modules/bluebird/js/release/promise.js:690:18)
at _drainQueueStep (/home/anoobbava/.nvm/versions/node/v9.9.0/lib/node_modules/electron-forge/node_modules/bluebird/js/release/async.js:138:12)
at _drainQueue (/home/anoobbava/.nvm/versions/node/v9.9.0/lib/node_modules/electron-forge/node_modules/bluebird/js/release/async.js:131:9)
at Async._drainQueues (/home/anoobbava/.nvm/versions/node/v9.9.0/lib/node_modules/electron-forge/node_modules/bluebird/js/release/async.js:147:5)
at Immediate.Async.drainQueues [as _onImmediate] (/home/anoobbava/.nvm/versions/node/v9.9.0/lib/node_modules/electron-forge/node_modules/bluebird/js/release/async.js:17:14)
at runCallback (timers.js:763:18)
at tryOnImmediate (timers.js:734:5)
at processImmediate (timers.js:716:5)
Other details are below,
OS: Ubuntu 18.04
node: v9.9.0
NPM: 6.4.1
I have updated my NPM version, but still, the issue persists. Also, Do I need to install yarn in this case.
Hi, @erickzhao this is my output with DEBUG:
$ DEBUG=electron-forge:* electron-forge make --platform=win32
⠋ Checking your system
✔ Checking your system
[STARTED] Loading configuration
electron-forge:project-resolver searching for project in: {pathToDir}/desktop-app +0ms
electron-forge:project-resolver package.json with forge dependency found in {pathToDir}/desktop-app/package.json +2ms
[SUCCESS] Loading configuration
[STARTED] Resolving make targets
electron-forge:require-search searching [
'@electron-forge/maker-squirrel',
'{pathToDir}/desktop-app/@electron-forge/maker-squirrel',
'{pathToDir}/desktop-app/node_modules/@electron-forge/maker-squirrel'
] relative to {pathToDir}/desktop-app +0ms
electron-forge:require-search testing @electron-forge/maker-squirrel +2ms
electron-forge:require-search searching [
'@electron-forge/maker-zip',
'{pathToDir}/desktop-app/@electron-forge/maker-zip',
'{pathToDir}/desktop-app/node_modules/@electron-forge/maker-zip'
] relative to {pathToDir}/desktop-app +40ms
electron-forge:require-search testing @electron-forge/maker-zip +0ms
electron-forge:require-search searching [
'@electron-forge/maker-deb',
'{pathToDir}/desktop-app/@electron-forge/maker-deb',
'{pathToDir}/desktop-app/node_modules/@electron-forge/maker-deb'
] relative to {pathToDir}/desktop-app +2ms
electron-forge:require-search testing @electron-forge/maker-deb +0ms
electron-forge:require-search searching [
'@electron-forge/maker-rpm',
'{pathToDir}/desktop-app/@electron-forge/maker-rpm',
'{pathToDir}/desktop-app/node_modules/@electron-forge/maker-rpm'
] relative to {pathToDir}/desktop-app +3ms
electron-forge:require-search testing @electron-forge/maker-rpm +0ms
[DATA] Making for the following targets: squirrel
[SUCCESS] Resolving make targets
[STARTED] Running package command
[STARTED] Preparing to package application
electron-forge:project-resolver searching for project in: {pathToDir}/desktop-app +59ms
electron-forge:project-resolver package.json with forge dependency found in {pathToDir}/desktop-app/package.json +4ms
[SUCCESS] Preparing to package application
[STARTED] Running packaging hooks
[STARTED] Running generateAssets hook
[SUCCESS] Running generateAssets hook
[STARTED] Running prePackage hook
[SUCCESS] Running prePackage hook
[SUCCESS] Running packaging hooks
[STARTED] Packaging application
[DATA] Determining targets...
electron-forge:packager packaging with options {
asar: false,
overwrite: true,
ignore: [ /^/out//g ],
quiet: true,
dir: '{pathToDir}/desktop-app',
arch: 'x64',
platform: 'win32',
afterFinalizePackageTargets: [ [AsyncFunction (anonymous)] ],
afterComplete: [ [AsyncFunction (anonymous)] ],
afterCopy: [ [AsyncFunction (anonymous)] ],
afterExtract: [ [AsyncFunction (anonymous)] ],
afterPrune: [ [AsyncFunction (anonymous)] ],
out: '{pathToDir}/desktop-app/out',
electronVersion: '18.3.15'
} +0ms
electron-forge:packager targets: [ { platform: 'win32', arch: 'x64' } ] +7ms
[STARTED] Packaging for x64 on win32
[STARTED] Copying files
[SUCCESS] Copying files
[STARTED] Preparing native dependencies
[TITLE] Preparing native dependencies
[SUCCESS] Preparing native dependencies
[STARTED] Finalizing package
[SUCCESS] Finalizing package
[SUCCESS] Packaging for x64 on win32
[SUCCESS] Packaging application
[STARTED] Running postPackage hook
electron-forge:packager outputPaths: [
'{pathToDir}/desktop-app/out/desktop-app-win32-x64'
] +8s
[SUCCESS] Running postPackage hook
[SUCCESS] Running package command
[STARTED] Running preMake hook
[SUCCESS] Running preMake hook
[STARTED] Making distributables
[STARTED] Making a squirrel distributable for win32/x64
[FAILED] An error occured while making for target: squirrel
[FAILED] An error occured while making for target: squirrel
An unhandled rejection has occurred inside Forge:
[object Object]
Electron Forge was terminated. Location:
error Command failed with exit code 1.
I have changed the log command and got the following error:
An unhandled rejection has occurred inside Forge:
{"message":"An error occured while making for target: squirrel","stack":"Failed with exit code: 255nOutput:nSystem.AggregateException: One or more errors occurred. () ---> System.Exceptionn at Squirrel.Utility.CreateZipFromDirectory (System.String zipFilePath, System.String inFolder) [0x00119] in <1ffb1a5dca5b4f2f93386cec56fd9ec2>:0 n --- End of inner exception stack trace ---n at System.Threading.Tasks.Task.ThrowIfExceptional (System.Boolean includeTaskCanceledExceptions) [0x00011] in <2c1f13c6f9ea4913bc0036d9d88cbeff>:0 n at System.Threading.Tasks.Task.Wait (System.Int32 millisecondsTimeout, System.Threading.CancellationToken cancellationToken) [0x00043] in <2c1f13c6f9ea4913bc0036d9d88cbeff>:0 n at System.Threading.Tasks.Task.Wait () [0x00000] in <2c1f13c6f9ea4913bc0036d9d88cbeff>:0 n at Squirrel.ReleasePackage.CreateReleasePackage (System.String outputFile, System.String packagesRootDir, System.Func2[T,TResult] releaseNotesProcessor, System.Action1[T] contentsPostProcessHook) [0x001f7] in <1ffb1a5dca5b4f2f93386cec56fd9ec2>:0 n at Squirrel.Update.Program.Releasify (System.String package, System.String targetDir, System.String packagesDir, System.String bootstrapperExe, System.String backgroundGif, System.String signingOpts, System.String baseUrl, System.String setupIcon, System.Boolean generateMsi, System.Boolean packageAs64Bit, System.String frameworkVersion, System.Boolean generateDeltas) [0x00214] in <1ffb1a5dca5b4f2f93386cec56fd9ec2>:0 n at Squirrel.Update.Program.executeCommandLine (System.String[] args) [0x00116] in <1ffb1a5dca5b4f2f93386cec56fd9ec2>:0 n at Squirrel.Update.Program.main (System.String[] args) [0x00113] in <1ffb1a5dca5b4f2f93386cec56fd9ec2>:0 n at Squirrel.Update.Program.Main (System.String[] args) [0x00006] in <1ffb1a5dca5b4f2f93386cec56fd9ec2>:0 n---> (Inner Exception #0) System.Exceptionn at Squirrel.Utility.CreateZipFromDirectory (System.String zipFilePath, System.String inFolder) [0x00119] in <1ffb1a5dca5b4f2f93386cec56fd9ec2>:0 <---nnnError: Failed with exit code: 255nOutput:nSystem.AggregateException: One or more errors occurred. () ---> System.Exceptionn at Squirrel.Utility.CreateZipFromDirectory (System.String zipFilePath, System.String inFolder) [0x00119] in <1ffb1a5dca5b4f2f93386cec56fd9ec2>:0 n --- End of inner exception stack trace ---n at System.Threading.Tasks.Task.ThrowIfExceptional (System.Boolean includeTaskCanceledExceptions) [0x00011] in <2c1f13c6f9ea4913bc0036d9d88cbeff>:0 n at System.Threading.Tasks.Task.Wait (System.Int32 millisecondsTimeout, System.Threading.CancellationToken cancellationToken) [0x00043] in <2c1f13c6f9ea4913bc0036d9d88cbeff>:0 n at System.Threading.Tasks.Task.Wait () [0x00000] in <2c1f13c6f9ea4913bc0036d9d88cbeff>:0 n at Squirrel.ReleasePackage.CreateReleasePackage (System.String outputFile, System.String packagesRootDir, System.Func2[T,TResult] releaseNotesProcessor, System.Action1[T] contentsPostProcessHook) [0x001f7] in <1ffb1a5dca5b4f2f93386cec56fd9ec2>:0 n at Squirrel.Update.Program.Releasify (System.String package, System.String targetDir, System.String packagesDir, System.String bootstrapperExe, System.String backgroundGif, System.String signingOpts, System.String baseUrl, System.String setupIcon, System.Boolean generateMsi, System.Boolean packageAs64Bit, System.String frameworkVersion, System.Boolean generateDeltas) [0x00214] in <1ffb1a5dca5b4f2f93386cec56fd9ec2>:0 n at Squirrel.Update.Program.executeCommandLine (System.String[] args) [0x00116] in <1ffb1a5dca5b4f2f93386cec56fd9ec2>:0 n at Squirrel.Update.Program.main (System.String[] args) [0x00113] in <1ffb1a5dca5b4f2f93386cec56fd9ec2>:0 n at Squirrel.Update.Program.Main (System.String[] args) [0x00006] in <1ffb1a5dca5b4f2f93386cec56fd9ec2>:0 n---> (Inner Exception #0) System.Exceptionn at Squirrel.Utility.CreateZipFromDirectory (System.String zipFilePath, System.String inFolder) [0x00119] in <1ffb1a5dca5b4f2f93386cec56fd9ec2>:0 <---nnn at ChildProcess.<anonymous> ({pathToDir}/packages/desktop-app/node_modules/electron-winstaller/lib/spawn-promise.js:49:24)n at ChildProcess.emit (node:events:527:28)n at ChildProcess.emit (node:domain:475:12)n at maybeClose (node:internal/child_process:1092:16)n at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)"}
An unhandled rejection has occurred inside Forge: Error: Could not find module with name: @electron-forge/maker-squirrel. Make sure it’s listed in the devDependencies of your package.json #2656
Comments
zheng834386282 commented Dec 27, 2021
Pre-flight checklist
- I have read the contribution documentation for this project.
- I agree to follow the code of conduct that this project uses.
- I have searched the issue tracker for a bug that matches the one I want to file, without success.
Electron Forge version
Electron version
Operating system
Windows 10 (1803)
Last known working Electron Forge version
Expected behavior
It would be packaged perfectly
Actual behavior

After I installed electron and forge, I wanted to package after completing the instructions in the above figure, but I always got the above error:
An unhandled rejection has occurred inside Forge:
Error: Could not find module with name: @electron-forge/maker-squirrel. Make sure it’s listed in the devDependencies of your package.json
Electron Forge was terminated. Location:
<>
But my package.json file shows that there is installation, as shown in another picture
Steps to reproduce
I have tried this step many times, but I always report this error in the npm run make step.
Additional information
The text was updated successfully, but these errors were encountered:
Источник
[5.x] weird error when running «electron-forge start» without node_modules #615
Comments
RossComputerGuy commented Nov 2, 2018
- I have read the contribution documentation for this project.
- I agree to follow the code of conduct that this project follows, as appropriate.
- I have searched the issue tracker for an issue that matches the one I want to file, without success.
Please describe your issue:
I’m getting this error when I run electron-forge start :
WARNING: DEBUG environment variable detected. Progress indicators will be sent over electron-forge:lifecycle
electron-forge:lifecycle Process Started: Checking your system +0ms
electron-forge:lifecycle Process Succeeded: Checking your system +184ms
electron-forge:runtime-config setting key: verbose to value: false +0ms
WARNING: DEBUG environment variable detected. Progress indicators will be sent over electron-forge:lifecycle
electron-forge:lifecycle Process Started: Locating Application +0ms
electron-forge:project-resolver searching for project in: /home/spaceboyross/paradise-client +0ms
electron-forge:project-resolver electron-forge compatible package.json found in /home/spaceboyross/paradise-client/package.json +19ms
electron-forge:lifecycle Process Succeeded: Locating Application +20ms
electron-forge:util Could not read package.json for moduleName=electron-prebuilt-compile < [Error: ENOENT: no such file or directory, open ‘/home/spaceboyross/paradise-client/node_modules/electron-prebuilt-compile/package.json’]
errno: -2,
code: ‘ENOENT’,
syscall: ‘open’,
path:
‘/home/spaceboyross/paradise-client/node_modules/electron-prebuilt-compile/package.json’ > +0ms
electron-forge:util Could not read package.json for moduleName=electron < [Error: ENOENT: no such file or directory, open ‘/home/spaceboyross/paradise-client/node_modules/electron/package.json’]
errno: -2,
code: ‘ENOENT’,
syscall: ‘open’,
path:
‘/home/spaceboyross/paradise-client/node_modules/electron/package.json’ > +4ms
electron-forge:util Could not read package.json for moduleName=electron-prebuilt < [Error: ENOENT: no such file or directory, open ‘/home/spaceboyross/paradise-client/node_modules/electron-prebuilt/package.json’]
errno: -2,
code: ‘ENOENT’,
syscall: ‘open’,
path:
‘/home/spaceboyross/paradise-client/node_modules/electron-prebuilt/package.json’ > +0ms
electron-forge:util getElectronVersion failed to determine Electron version: projectDir=/home/spaceboyross/paradise-client, result=null +0ms
electron-forge:lifecycle Process Started: Preparing native dependencies +11ms
electron-forge:lifecycle Process Failed: Preparing native dependencies +2ms
An unhandled error has occurred inside Forge:
Expected a string version for electron version, got a «object»
Error: Expected a string version for electron version, got a «object»
at new Rebuilder (/home/spaceboyross/.nvm/versions/node/v11.0.0/lib/node_modules/electron-forge/node_modules/electron-rebuild/lib/src/rebuild.js:62:19)
at rebuildWithOptions (/home/spaceboyross/.nvm/versions/node/v11.0.0/lib/node_modules/electron-forge/node_modules/electron-rebuild/lib/src/rebuild.js:316:23)
at doRebuild (/home/spaceboyross/.nvm/versions/node/v11.0.0/lib/node_modules/electron-forge/node_modules/electron-rebuild/lib/src/rebuild.js:323:16)
at /home/spaceboyross/.nvm/versions/node/v11.0.0/lib/node_modules/electron-forge/dist/util/rebuild.js:27:57
at Generator.next ()
at Generator.tryCatcher (/home/spaceboyross/.nvm/versions/node/v11.0.0/lib/node_modules/electron-forge/node_modules/bluebird/js/release/util.js:16:23)
at PromiseSpawn._promiseFulfilled (/home/spaceboyross/.nvm/versions/node/v11.0.0/lib/node_modules/electron-forge/node_modules/bluebird/js/release/generators.js:97:49)
at /home/spaceboyross/.nvm/versions/node/v11.0.0/lib/node_modules/electron-forge/node_modules/bluebird/js/release/generators.js:201:15
at /home/spaceboyross/.nvm/versions/node/v11.0.0/lib/node_modules/electron-forge/dist/util/rebuild.js:53:22
at _promise2.default (/home/spaceboyross/.nvm/versions/node/v11.0.0/lib/node_modules/electron-forge/dist/util/ora-handler.js:46:5)
at new Promise ()
at new F (/home/spaceboyross/.nvm/versions/node/v11.0.0/lib/node_modules/electron-forge/node_modules/core-js/library/modules/_export.js:36:28)
at asyncOra (/home/spaceboyross/.nvm/versions/node/v11.0.0/lib/node_modules/electron-forge/dist/util/ora-handler.js:45:10)
at /home/spaceboyross/.nvm/versions/node/v11.0.0/lib/node_modules/electron-forge/dist/util/rebuild.js:25:36
at Generator.next ()
at Generator.tryCatcher (/home/spaceboyross/.nvm/versions/node/v11.0.0/lib/node_modules/electron-forge/node_modules/bluebird/js/release/util.js:16:23)
«forge»: <
«make_targets»: <
«win32»: [
«squirrel»
],
«darwin»: [
«zip»
],
«linux»: [
«deb»,
«rpm»
]
>,
«electronPackagerConfig»: <
«packageManager»: «npm»
>,
«electronWinstallerConfig»: <
«name»: «Paradise»
>,
«electronInstallerDebian»: <>,
«electronInstallerRedhat»: <>,
«github_repository»: <
«owner»: «»,
«name»: «»
>,
«windowsStoreConfig»: <
«packageName»: «Paradise»,
«name»: «paradise-client»
>
>
The text was updated successfully, but these errors were encountered:
Источник
Fresh install fails with node-abi error #1473
Comments
ospfranco commented Feb 4, 2020
Preflight Checklist
- [x ] I have read the contribution documentation for this project.
- [ x] I agree to follow the code of conduct that this project follows, as appropriate.
- [x ] I have searched the issue tracker for a bug that matches the one I want to file, without success.
Issue Details
- Electron Forge Version:
- Electron Version:
- Operating System:
- Last Known Working Electron Forge version::
Expected Behavior
Started a brand new project using both the yarn command and the npx commandnpx create-electron-app foo —template=typescript
after cding into the directory and executing yarn start or npm start I get greeted with this very nice message:
An unhandled error has occurred inside Forge:
Could not detect abi for version 8.0.0 and runtime electron. Updating «node-abi» might help solve this issue if it is a new release of electron
Error: Could not detect abi for version 8.0.0 and runtime electron. Updating «node-abi» might help solve this issue if it is a new release of electron
Actual Behavior
To Reproduce
Start a brand new project and try to start it.
Additional Information
The text was updated successfully, but these errors were encountered:
Источник
[5.x] cannot install npm dependencies #1419
Comments
karthik22061993 commented Jan 16, 2020 •
I tried create electron app using elctron-forge. I see following error, has anyone tried to create electron app using electron-forge before?
Electron-forge version is 5.2.4
Electron — v5.0.6
The text was updated successfully, but these errors were encountered:
malept commented Jan 16, 2020
Use the instructions on https://electronforge.io to create a new Electron project.
karthik22061993 commented Jan 16, 2020
npx create-electron-app demoCLS
√ Initializing Project Directory
√ Initializing Git Repository
√ Locating custom template: «base»
√ Copying Starter Files
√ Initializing NPM Module
√ Installing Template Dependencies
× Installing NPM Dependencies
An unhandled error has occurred inside Forge:
Failed to install modules: [«electron-squirrel-startup»]
With output: Exited with status 1
error An unexpected error occurred: «EISDIR: illegal operation on a directory, read».
Error: Failed to install modules: [«electron-squirrel-startup»]
With output: Exited with status 1
error An unexpected error occurred: «EISDIR: illegal operation on a directory, read».
karthik22061993 commented Jan 16, 2020
I followed the doc ,this is what I see and npm start shows this
npm start
democls@1.0.0 start C:demoCLSdemoCLSdemoCLS
electron-forge start
√ Checking your system
× Locating Application
Electron forge was terminated:
You must depend on «electron-prebuilt-compile» in your devDependencies
malept commented Jan 16, 2020
«EISDIR: illegal operation on a directory, read».
Make sure you’re doing creating a new Electron app with a nonexisting directory.
You must depend on «electron-prebuilt-compile» in your devDependencies
This usually means that you already tried to create an Electron Forge v5 project. You should use a new directory to create an Electron Forge v6 project.
karthik22061993 commented Jan 16, 2020
npx create-electron-app my-app
Here ‘my-app’ didn’t exist before,
× Installing NPM Dependencies
An unhandled error has occurred inside Forge:
Failed to install modules: [«electron-squirrel-startup»]
With output: Exited with status 1
error An unexpected error occurred: «EISDIR: illegal operation on a directory, read».
Error: Failed to install modules: [«electron-squirrel-startup»]
With output: Exited with status 1
error An unexpected error occurred: «EISDIR: illegal operation on a directory, read».
Источник
Empty output when trying to create a Squirrel distributable #315
Comments
PabloPG commented Sep 4, 2017
- I have read the contribution documentation for this project.
- I agree to follow the code of conduct that this project follows, as appropriate.
- I have searched the issue tracker for an issue that matches the one I want to file, without success.
Please describe your issue:
When I try to create an installer for the application, an error occurs without description
Console output when you run electron-forge with the environment variable DEBUG=electron-forge:* . (Instructions on how to do so here). Please include the stack trace if one exists.
What does your config.forge data in package.json look like?
Please provide either a failing minimal testcase (with a link to the code) or detailed steps to
reproduce your problem. Using electron-forge init is a good starting point, if that is not the
source of your problem.
The text was updated successfully, but these errors were encountered:
malept commented Sep 4, 2017
Try running SET DEBUG=electron-windows-installer:* and then electron-forge make . That should give a little more debug output.
PabloPG commented Sep 5, 2017
Same error.
(windows-installer)
malept commented Sep 5, 2017
PabloPG commented Sep 5, 2017
With debug detected
MarshallOfSound commented Sep 5, 2017
There should be a Squirrel log somewhere (I think the out directory) telling you what went wrong
PabloPG commented Sep 5, 2017
malept commented Sep 5, 2017
Use $env:DEBUG = «electron-forge:*,electron-windows-installer:*» instead.
PabloPG commented Sep 7, 2017
the same thing, output goes blank
malept commented Sep 7, 2017
I think at this point you’re going to have to debug what application in electron-winstaller it’s failing on. I would add some console.log statements before spawn calls to figure it out.
malipetek commented Sep 17, 2017 •
I got the same error. It went away when I chaged «electronWinstallerConfig».
It was:
and now it is:
I figured out simply this was because squirrel can not pack when it cant find icons.
this configuration worked with electron-forge make —arch=ia32 and with custom installtion gif:
Whenever I put 💢 setupIcon 💢 parameter I got the same error.
Источник
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
Я начал учиться в электронном виде, воспользовавшись обучением по запросу на GitHub. Когда я выполнил следующую команду. Система выдает ошибку.
electron % electron-forge init electron-app
⚠ Could not check Yarn version "0.32
", assuming incompatible
⚠ You are using Yarn, but not a known good version.
The known versions that work with Electron Forge are: 0.23.3 || 0.24.6 || >= 1.0.0 || 0.27.5
✔ Checking your system
? WARNING: The specified path: "/home/anoobbava/electron/electron-app" is not empty, do you wish to continue? Yes
✔ Initializing Project Directory
✔ Initializing Git Repository
✔ Copying Starter Files
✔ Initializing NPM Module
✖ Installing NPM Dependencies
An unhandled error has occurred inside Forge:
Failed to install modules: ["electron-compile","electron-squirrel-startup"]
With output: Exited with status 1
Error: Failed to install modules: ["electron-compile","electron-squirrel-startup"]
With output: Exited with status 1
at /home/anoobbava/.nvm/versions/node/v9.9.0/lib/node_modules/electron-forge/dist/util/install-dependencies.js:55:13
at Generator.throw (<anonymous>)
at Generator.tryCatcher (/home/anoobbava/.nvm/versions/node/v9.9.0/lib/node_modules/electron-forge/node_modules/bluebird/js/release/util.js:16:23)
at PromiseSpawn._promiseRejected (/home/anoobbava/.nvm/versions/node/v9.9.0/lib/node_modules/electron-forge/node_modules/bluebird/js/release/generators.js:107:10)
at Promise._settlePromise (/home/anoobbava/.nvm/versions/node/v9.9.0/lib/node_modules/electron-forge/node_modules/bluebird/js/release/promise.js:576:26)
at Promise._settlePromise0 (/home/anoobbava/.nvm/versions/node/v9.9.0/lib/node_modules/electron-forge/node_modules/bluebird/js/release/promise.js:614:10)
at Promise._settlePromises (/home/anoobbava/.nvm/versions/node/v9.9.0/lib/node_modules/electron-forge/node_modules/bluebird/js/release/promise.js:690:18)
at _drainQueueStep (/home/anoobbava/.nvm/versions/node/v9.9.0/lib/node_modules/electron-forge/node_modules/bluebird/js/release/async.js:138:12)
at _drainQueue (/home/anoobbava/.nvm/versions/node/v9.9.0/lib/node_modules/electron-forge/node_modules/bluebird/js/release/async.js:131:9)
at Async._drainQueues (/home/anoobbava/.nvm/versions/node/v9.9.0/lib/node_modules/electron-forge/node_modules/bluebird/js/release/async.js:147:5)
at Immediate.Async.drainQueues [as _onImmediate] (/home/anoobbava/.nvm/versions/node/v9.9.0/lib/node_modules/electron-forge/node_modules/bluebird/js/release/async.js:17:14)
at runCallback (timers.js:763:18)
at tryOnImmediate (timers.js:734:5)
at processImmediate (timers.js:716:5)
Другие подробности ниже, ОС: Ubuntu 18.04, узел: v9.9.0 NPM: 6.4.1 Я обновил свою версию NPM, но проблема все еще сохраняется. Кроме того, мне нужно установить пряжу в этом случае.
1 ответ
Лучший ответ
У меня была аналогичная проблема, и в итоге она была связана с версией пряжи. Я исправил это, установив пряжу следующим образом:
sudo npm install --global yarn
3
Amine Kerkeni
16 Фев 2019 в 12:55
Logs (Most issues require logs to diagnose):
Spoiler
Please post logs using one of the following sites (Thank you Lumber Wizard for the list):
https://gist.github.com/: 100MB Requires member (Free)
https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)
https://hastebin.com/: 400KB
Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.
What to provide:
…for Crashes and Runtime issues:
Minecraft 1.14.4 and newer:
Post debug.log
Older versions:
Please update…
…for Installer Issues:
Post your installer log, found in the same place you ran the installer
This log will be called either installer.log or named the same as the installer but with .log on the end
Note for Windows users:
Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension
Where to get it:
Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraftlogs.
Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge’s log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse’s installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:
Spoiler
- Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
- Make a launcher profile targeting this version of Forge.
- Set the launcher profile’s GameDir property to the pack’s instance folder (not the instances folder, the folder that has the pack’s name on it).
- Now launch the pack through that profile and follow the «Mojang Launcher» instructions above.
Video:
Spoiler
or alternately,
Fallback («No logs are generated»):
If you don’t see logs generated in the usual place, provide the launcher_log.txt from .minecraft
Server Not Starting:
Spoiler
If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output.
Reporting Illegal/Inappropriate Adfocus Ads:
Spoiler
Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad.
Lex will need the Ad ID contained in that URL to report it to Adfocus’ support team.
Posting your mod as a GitHub Repo:
Spoiler
When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub.
When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.
- Open a command prompt (CMD, Powershell, Terminal, etc).
- Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
-
Run the following commands:
- git init
-
git remote add origin [Your Repository’s URL]
- In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git
- git fetch
- git checkout —track origin/master
- git stage *
- git commit -m «[Your commit message]»
- git push
-
Navigate to GitHub and you should now see most of the files.
- note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from)
- Now you can share your GitHub link with those who you are asking for help.
[Workaround line, please ignore]


