-
Notifications
You must be signed in to change notification settings - Fork 194
feat: prebuild binaries for electron and node #67
Conversation
You will need to add
|
What is the reason for switching from npm to yarn? |
@50Wliu As maintainer of electron-builder, I am tired to advice users "remove node_modules and npm install again". Yarn fast and reliable. electron-userland/electron-builder#1610 (comment) |
@50Wliu will this PR merged in a near future ? I'm very interested in having prebuild binaries to generate my electron application easily. And thanks to develar for his work ! |
@popod for now you can use keytar-prebuild, but of course we need official release. |
@develar does Thanks for answer and sorry for the off topic.. |
@popod 1.7.5 doesn't introduce new ABI version (upcoming 1.8.0 does, but not yet released).
Not automatic. Developer need to set version explicitly. Maybe automated, but... it occurs only ~ once a half year :) |
@popod I can't say. I'm not familiar with this repository. |
When running unit tests with karma, I've this error:
What should be the problem ? |
@popod it seems in your project you use webpack and forget to add node-loader plugin. |
@develar Thanks.. I've installed it and this works.. but this is strange : without keytar, running the unit tests works well without installing node-loader. |
@popod Nothing strange — keytar is a native module, so, there is |
Rebased and Electron 1.8.0 support was added. I hope you will find time to make Electron developer's life more easier. |
Ping :) |
@zeke maybe you can review and accept this PR? |
I'm in support of the idea of using prebuild, but it would be the Atom team's call on whether to ship and maintain this. None of the other Atom projects are using yarn, so I think sticking to npm would mean less disruption and give you better odds of getting this PR merged. Also we unpublished electron 1.8.0 due to a security vulnerability, so this would need to be updated when 1.8.1 lands. (Shooting for a release of that very soon.) cc @shiftkey, whom I know to be a user of keytar in https://github.com/desktop/desktop. |
It doesn't matter (because ABI version will be the same, if I am not wrong). |
What's up here? Go npm if you want, but it will save a lof a time to get that merged :) |
I'm okay with landing this, assuming the requested yarn->npm changes are made to be consistent with the rest of the projects in the atom org. |
It's a shame to see that this is held back because of a yarn vs npm debate. |
👋 Thanks for the interest everyone. With the holidays approaching, lots of efforts are being put on hold for the next couple weeks. Additionally, we're planning on transitioning and re-evaluating how the Atom team handles some things in January. Given all of that, it is unlikely that the Atom team will make a decision on whether to take this on or not until late January at the earliest. It's on my list of things to bring up when things start getting picked up again in the new year. So if you have any questions at that point let me know and I'll see what I can do to get them answered. |
As workaround, for now you can use fork |
@develar Happy new year and huge thank you for providing prebuilt binaries for keytar! With the recent release of 4.1.0 there is a new function, |
- Fix Electron linting errors. - Add brew update to build script for getting latest dependencies versions. - Clean .gitignore to remove IDE specific ignores and old rules. - Add productName to build config. - Replace dependency keytar with keytar-prebuild until atom/node-keytar#67 is not merged.
# Conflicts: # package-lock.json
@daviwil Branch updated, deps updated. Feel free to push to my branch. |
Thanks for jumping in on this, @daviwil. 👍 |
Tried this out yesterday, looks great! I'll make a couple tweaks so that it only does prebuilds for tags and then I'll get it merged today. |
By the way, were the version bumps of babel-core, etc necessary, or was that Yarn's doing? I'd guess it was the latter. |
I updated deps. To make explicit that tested on this dependency versions. |
.npmignore
Outdated
@@ -1,9 +0,0 @@ | |||
/build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe this file needs to be added back.
Thanks so much for putting this together @develar! We'll be providing prebuilds in the next release of node-keytar today or tomorrow :) |
v4.2.0 is out, please give it a shot and let me know if you run into any issues! |
Hi, Ive tried "npm install keytar-prebuild", works fine, but then I still have "Uncaught Error: A dynamic link library (DLL) initialization routine failed." error when I run my electron app using "npm start". Any idea? os: windows 8.1 pro (x64) |
@IndieRobert why |
@vladimiry thx for helping. Tried that as well, didnt work, same error. (spec updated on previous comment) |
@develar created npm deprecate keytar-prebuild@"*" -m "keytar-prebuild is no longer maintained. Use `keytar` instead." |
Closes #27
keytar-prebuild
and Electron app that built on Travis CI macOS works on Windows.electron-userland/electron-builder
is automated (not manual) build, so, you can be sure that image is built on Docker Cloud machine from sources.