-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Application entry can't be found #371
Comments
Try setting "main" property in your root package.json to be "app/index.js" |
@Vj3k0 Fix will be tomorrow, for now I suggest just set version to |
@caibirdme Cannot reproduce. Test passed for me. Notes:
@demetris-manikas Maybe do you have any idea? |
@caibirdme is there an app.asar being built? If so could you provide the output of asar list app.asar? |
@caibirdme can you also please explain what is the "electron" listing in your app folder? |
@demetris-manikas I think it maybe a problem of asar...if I add |
@caibirdme can you also answer to my previous question as well? |
You can use externalResources to set data which needs to be accessed outside of asar. Asar is not considered a folder so path is broken to resource which is packed in it. |
@demetris-manikas Sorry for my late reply,I was busy completing my dissertation.There is a app.asar in the foo.app/Contents/Resource.and when I ran |
@Vj3k0 I use |
@caibirdme asar app.asar doesn't output anything anyway. Try running
|
@demetris-manikas list command return an error.
|
@caibirdme So it seems that electron-builder error message is misleading and should be fixed (I 'll create a PR soon). |
Still get that error. and the asar file is empty, if I run |
@gamestailer94 I saw that you reverted to electron-builder 3.11. |
Still empty, was just somethink i tryed in hope that it will wor. |
@gamestailer94 Good. This is why the warning is there. To safeguard you from publishing a "successful" build. I 'll try to reproduce and I' ll get back to you. |
@gamestailer94 Can you please try setting the packageName equal to name in app/package.json and try again? There is an open bug (#360) when defining different values for the two. |
@demetris-manikas We should use productName in all cases except publish (we provide special names for publisher) and specific Linux cases. In the code If we have |
Can Confirm if ProductName and name are indetical it works |
@demetris-manikas I will do it. It will be not warning, but error — just because it doesn't work in any case. |
Duplicate #360 @demetris-manikas Thanks for investigation. |
@develar gamestailer94's problem has to do with another thing. gamestailer94 used as productName a value like "[QS] blah blah" and after investigating it turned out that the directory name is used by asar as a RegExp to find the files to add in the asar ( if [] exists the RegEpx fails to list anything and thus the empty asar file. |
After giving a thought the pattern as source is an asar's feature so I wont be fileing a PR there. Would you like me to file a PR at electron-packager-tf ? |
@demetris-manikas Proper fix should be not escaping, but disable RegExp handling on asar side.
It is a pitfall. We pass path as path, not pattern. And should be simple way to disable regex instead of trying to escape it. |
@develar Point taken. I 'll PR at asar and see what happens. |
PR created. electron/asar#68 |
@develar I don't fight with anyone. I am just proposing a solution to a problem. Escaping the directory in electron-packager is for me the right solution. The problem is clear and the fix as well. You take it from here. :) |
Awesome avatar 😂 @caibirdme |
@fritx Thx for ur praise |
Hey,all
I followed the two package.json structure in the document, but when I ran
npm run build
, it reported an error thatApplication entry file couldn't be found in package.Seems like a wrong configuration
the package.json in the root of the project is:
and the structure of app directory is:
the package.json in app directory is:
version:
node 5.10.0
npm 3.8.3
electron 0.37.5
electron-builder 3.13.1
The text was updated successfully, but these errors were encountered: