-
-
Notifications
You must be signed in to change notification settings - Fork 535
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Creating/Starting new project fails with error "Error: Electron version 1.4.15 is either too old or too new" #148
Comments
It looks like we've lost some lines of the error trace including the message itself. Can you add those back in. Initial idea though is you are using babel-env and simply need to update it to a newer version |
Sorry for the improper formatting of my error message. I've updated it and made sure the whole message appears. |
Yeah, looks like my guess was on the right path. Can you try blowing away your node_modules folder and reinstalling. (How long ago did you create this app?) Can you also post your .compilerc |
Seeing a similar error on an app $ electron-forge start
✔ Checking your system
✔ Locating Application
✔ Preparing native dependencies
✔ Launching Application
App threw an error during load
Error: Electron version 1.4.15 is either too old or too new (While processing preset: "/Users/creed/Sites/electron-forge-test/node_modules/babel-preset-env/lib/index.js")
at getTargets (/Users/creed/Sites/electron-forge-test/node_modules/babel-preset-env/lib/index.js:144:13)
at buildPreset (/Users/creed/Sites/electron-forge-test/node_modules/babel-preset-env/lib/index.js:209:17)
at /Users/creed/Sites/electron-forge-test/node_modules/babel-core/lib/transformation/file/options/option-manager.js:317:46
at Array.map (native)
at OptionManager.resolvePresets (/Users/creed/Sites/electron-forge-test/node_modules/babel-core/lib/transformation/file/options/option-manager.js:275:20)
at OptionManager.mergePresets (/Users/creed/Sites/electron-forge-test/node_modules/babel-core/lib/transformation/file/options/option-manager.js:264:10)
at OptionManager.mergeOptions (/Users/creed/Sites/electron-forge-test/node_modules/babel-core/lib/transformation/file/options/option-manager.js:249:14)
at OptionManager.init (/Users/creed/Sites/electron-forge-test/node_modules/babel-core/lib/transformation/file/options/option-manager.js:368:12)
at File.initOptions (/Users/creed/Sites/electron-forge-test/node_modules/babel-core/lib/transformation/file/index.js:216:65)
at new File (/Users/creed/Sites/electron-forge-test/node_modules/babel-core/lib/transformation/file/index.js:139:24) The process hangs. Here’s the .compilerc: {
"env": {
"development": {
"application/javascript": {
"presets": [
[
"env",
{
"targets": {
"electron": "1.4.15"
}
}
],
"react"
],
"plugins": [
"transform-async-to-generator"
],
"sourceMaps": "inline"
}
},
"production": {
"application/javascript": {
"presets": [
[
"env",
{
"targets": {
"electron": "1.4.15"
}
}
],
"react"
],
"plugins": [
"transform-async-to-generator"
],
"sourceMaps": "none"
}
}
}
} Relevant stats:
|
Blowing away node_modules and re-installing produces an identical error. 😱 |
Having the same error tried upgrading to electron v1.6.1 and now have the following message
|
The workaround is: pin |
I figured that the version of |
haha^^ to late :) |
@janwiemers yeah, I think you're right, my guess is that babel/babel-preset-env#144 is causing it. |
I think I can make a PR to |
People affected by this bug, please use the workaround in my earlier comment until Kilian/electron-to-chromium#4 is merged & released. |
This bug should be fixed! I have verified it on the app I was using to test the behavior. Please let me know if this specific error still persists after running |
@malept yeah I can confirm it's working fine now. |
fix: Ensure correct version selection & display
Please describe your issue:
Created a new application, started the application and received the following error:
Console output when you run
electron-forge
with the environment variableDEBUG=electron-forge:*
. (Instructions on how to do so here). Please include the stack trace if one exists.What command line arguments are you passing?
What does your
config.forge
data inpackage.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 thesource of your problem.
The text was updated successfully, but these errors were encountered: