-
-
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
Turn off node_modules deps resolving or the warning about missing deps #2551
Comments
Please see Packager.productionDeps getter. I guess here we should check is node_modules dir exist if |
Sth like this wojtkowiak@bbacd3e ? But maybe better to condition this also with and additional env var? |
Yep (except that I think no need to
No, no pleasure for users to guess such env instead of just "build my app". |
Totally agree: wojtkowiak@17d33ea Should I add a note in the docs about it somewhere? Maybe in the |
👍 |
I can't find any mention of this option in the current version. Is there some other way to not get electron-builder to check for missing deps? Our CI log ends up with nearly 600,000 lines because of all the unresolved deps spam in the logs, so looking for a solution to suppress it. |
Hey,
I am in the proces of updating
[email protected]
to the newest one inmeteor-desktop
.I did mention in the past 🙂 (#982 (comment)) that I am packing my node_modules into asar before building installer. Now
electron-builder
is complaining about unresolved deps asnode_modules
is not present at the time it processes the app.I know that I can set the
ELECTRON_BUILDER_ALLOW_UNRESOLVED_DEPENDENCIES
but is still gives a warning (#982 (comment))Would you add an option to disable this mechanism or at least disable this warning in any way?
Of course I can prepare the PR but just let me know how would you prefer this to be realised?
The text was updated successfully, but these errors were encountered: