-
-
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
Dependencies are not packaged by electron-builder when using pnpm #6289
Comments
@develar can you please take a look at this when you have a chance? |
Run into same problem, the |
Any updates? |
Hey guys! |
I don't have plans to implement the support for pnp. But I'd happily review PRs for it! 🙂 |
Same here, would be awesome to have support for it |
Quick test, can someone try setting
|
I tried the |
@develar really could use your help on this one. Seems to be failing with I've tried other alternatives for reading dependency trees and they aren't viable. I'm not sure how app-builder works, but it seems like it just needs to also search |
Choose any of them. The problem will be solved. Update: If your dependencies have multiple versions, it's best to add |
Same. Would really love to see it is supported. |
@BlackHole1 thanks for the suggested solution. This is probably an acceptable solution for some however the suggested approach is basically throwing away the benefits of using pnpm in the first place. The repo's readme also links to a comment about why yarn should be used however with 129 downvotes and 94 confused emojis it's clearly not backed by the community running into these issues. I'm not able to provide a better solution myself but I'd like to point out how much of a hurdle this is for adoption. We're not prepared to relax the reliability of our dependency system that pnpm brings to our monorepo. Changing this for a single package is an unreasonable ask. I hope there is a path forward soon; A fundamental library shouldn't have to compromise it's audience based on a package manager. |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Any progress here? |
Issue is in upstream dependency app-builder (node_modules/app-builder-bin) Workaround is: #6289 (comment) |
I'm having issues trying to use pnpm and electron-builder. I tried multiple times to package the app using basic commands and build configurations from online guides but i would always get dependency related errors after packaging it.
Initially i thought it was my configuration error, but after copying the whole project and used npm instead, everything worked as expected.
From what i could find, it seems that electron-builder can't resolve the dependencies within the .pnpm folder, but i am not 100% certain of this.
pnpm and electron-builder are both great would love to have this fixed
Build config
Using pnpm
As shown in the screenshot, semver already exist in node_modules/.pnpm
Using npm with same exact build config
Application is built with no errors by electron-builder
The text was updated successfully, but these errors were encountered: