| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
I think node-gyp is broken also with iojs@3.0, @gabeio @coderaiser can you take a look here paulmillr/chokidar#329? |
Sorry, something went wrong.
|
@iamstarkov I am having build issues with iojs 3 also... but sidenote you may be able to build it with 2.5.0 or lower and still use the package in 3.0.0 nevermind you can't 😢 |
Sorry, something went wrong.
There was a problem hiding this comment.
This may not reliable if NodeJS released v1.0.0 someday, I prefer process.release.node === 'io.js'.
Sorry, something went wrong.
There was a problem hiding this comment.
"Node.js" 1.0.0 will never be released. As a TSC member, I can authoritatively say that. :)
Also, io.js is node.js now: https://github.com/nodejs/node
However, version detection still isn't a great way of doing things, though it could for for io.js 1.0.0> <3.0.0. As @camsong said, what we really should be doing now is detecting 3.0.0's process.release :)
Sorry, something went wrong.
|
As a workaround, you can build against electron and end up with binaries that also load into vanilla iojs: $ npm install electron-prebuilt -g $ npm install electron-updater-tools -g $ elb configure The last command runs a script in the electron-updater-tools project that uses a --dist-url for electron that is compatible with node-gyp. It uses a delay load hack to make the binaries compatible with electron and iojs/node. I ideally this would be fixed in node-gyp directly. Also related to this PR: #653 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Add iojs support: when version >=1.0.0 download dist from url https://iojs.org.