-
Notifications
You must be signed in to change notification settings - Fork 263
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
Electron runtime detection #188
Comments
Thanks, @es128! |
Any updates on this issue? I can see that the two PR's are still open. Anything that I can do to help get one of them accepted? |
Hi! I'm really struggling with using chokidar -> fsevents -> node-pre-gyp in an Atom plugin. apm rebuild still fails for me. Repro is as simple as downloading Atom and running apm rebuild on fsevents. I reported here: but maybe here is a better place to ask? Seems the open issues just lie around… |
We've fix that is now in the released v0.6.26 (#187) |
@springmeyer I guess you mean 0.6.25? I got hopeful here when I saw this released and the following release of fsevents using this (thanks @es128 ). But fsevents still fails with node-pre-gyp with 0.6.25 using apm rebuild:
|
From: fsevents/fsevents#93 (comment) (//cc @stdavis)
node-pre-gyp does not appear to try to auto-detect electron:
node-pre-gyp/lib/util/versioning.js
Line 252 in 2e5590a
When the install command is baked in to a package, how would an end-user be able apply the equivalent of
--runtime=electron
in order to prevent theirnpm install
from barfing?The text was updated successfully, but these errors were encountered: