-
-
Notifications
You must be signed in to change notification settings - Fork 536
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
babel-preset-env 1.3.0 throws "Target version must be a number" when forge start
is run
#186
Comments
This broke with babel/babel-preset-env#229, I'm trying to figure out how to fix it. |
I saw the other issues with different versions of node, I blew away the node-modules folder and reinstalled the packages to no avail. I also tried the install without the react framework, same problem. |
Until I figure out how to fix this, in your Electron project, fix the |
let me try it and I will get back to you in a moment |
forge start
is run
;-(( NOPE! |
Make sure babel-preset-env has 1.2.2 installed and not 1.3.0. This is my repro instructions:
|
alright, I will admit I am now confused. |
well that did not work (blowing away the modules folder) now I get another weird message. I am going to restart the process.. (yes I am new at this) |
OK we have lift off! i will let you decide to close the ticket, attach it to the other error or leave it open. Thanks @malept for all your help, now I can start to play with react!! |
I had the same issue few hours ago. Notice also that changing |
Yes, babel-preset-env no longer allows string versions for Electron, I hope they fix that. |
New projects in Forge no longer have this problem as of 2.9.0. It uses a Number for the Electron version instead of a String. |
I am unsure how to fix this problem with a project created in an older version of forge? I blew away node_modules and updated forge to 2.9.0 and still get
Here are dependencies
|
Use @gimyboya's solution for existing projects. The change needs to be in |
OK. I am assuming that since the fix is in .compilerc that I will need to recompile? Is there anyway to force forge to do so without blowing away node_modules? Thanks |
No, you won't need to recompile. Does it matter? |
Nope recompile does not matter. I was just curious. @gimyboya 's solution did work for me. It will only work with major/minor e.g. 1.6 and not 1.6.2. The latter causes a parse error in the json. Not exactly sure why, but it is not affecting me. Thanks for the help. I am up and running again. 👍 |
Please describe your issue:
I just created a new app per the instructions on the read me.
I set the template to be react and it all installed
I then did an npm install to get the remaining dependencies and from my command window ran: npm start.
And this is the error I received below.
FYI I am running on Windows10 and node is v6.10.0
Here is the output WITHOUT the debug variable
What command line arguments are you passing? NONE
What does your
config.forge
data inpackage.json
look like? (did not change it)The text was updated successfully, but these errors were encountered: