-
-
Notifications
You must be signed in to change notification settings - Fork 111
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
Existing Ember project not launching with ember electron
#51
Comments
Thanks for reporting! I'ts a bit hard to see because of the whiteouts, but is there a comma in the app name? I'd assume that the trouble is that the app and the generator disagree over where the app is located. To fix:
|
Oh, and if you changed your app's name, you should probably run ember g ember-electron again. |
Yeah sorry about the white out 😁 those are actually the letter y and the name is made up of just letters and - ? Any other ideas? |
It's definitely the app name - or, if you're sure that the files are there on disk, you might have an error in that file that keeps it from being successfully exported. |
Which file would have the error? |
for me, with the same versions and OS, the electron app is just shown in the dock but no app window pops up :( No errors too. I tried packaging it and opening the executable but still the same. And to add to this information, the tests ember electron:test work just fine. Just not the app itself Update: I forgot I was pointing to some express-server accommodating code. I probably need to re-try |
I also was able to run the tests fine not sure why one would run and the other not |
Closing due to age; please do reopen if this is still an issue 😄 |
Here is my current versions
package.json electron dependency versions
"electron-packager": "6.0.0",
"electron-prebuilt": "0.37.5",
"electron-rebuild": "1.1.3",
"ember-electron": "1.3.2",
$ ember -v
ember-cli: 2.4.3
node: 4.4.2
os: darwin x64
After running
ember install ember-electron
and configuring project trying to runember electron
gives me this:The text was updated successfully, but these errors were encountered: