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
Prebuilt binaries for node:9 are not available #122
Comments
Prebuilds for linux/macosx uploaded. Windows failed: https://ci.appveyor.com/project/fanatid/secp256k1-node/build/52/job/983whoxs37ojxcjg |
I don't normally do development on windows, but I installed https://gist.github.com/vith/5aa4c9e1a08db488cd52bcd7ea740fcc |
Can you do same for 9.0.0? |
Thanks, I started build for 9.1 on appveyor, will see soon. https://ci.appveyor.com/project/fanatid/secp256k1-node |
I was able to reproduce the failure like this: PS C:\Users\vith\Desktop\New folder> npm install npm@latest
npm WARN saveError ENOENT: no such file or directory, open 'C:\Users\vith\Desktop\New folder\package.json'
npm WARN enoent ENOENT: no such file or directory, open 'C:\Users\vith\Desktop\New folder\package.json'
npm WARN New folder No description
npm WARN New folder No repository field.
npm WARN New folder No README data
npm WARN New folder No license field.
+ npm@5.5.1
added 460 packages in 6.08s
PS C:\Users\vith\Desktop\New folder> .\node_modules\.bin\npm install secp256k1
npm WARN npm npm does not support Node.js v9.0.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8.
npm WARN npm You can find the latest version at https://nodejs.org/
C:\Program Files\nodejs\node.exe: src\node_zlib.cc:430: Assertion `args.Length() == 7 && "init(windowBits, level, memLevel, strategy, writeResult, writeCallback," " dictionary)"' failed. See also npm/npm#19019 (comment) Seems you need to avoid doing |
@vith thank you! pushed with yarn :)) |
Seems like this was undone with 9724304 Was that intentional? |
Unfortunately or not, yes, this was intentional. |
It's just an annoyance that it has to be rebuilt all the time because npm/yarn don't cache the result of node-gyp building it. In CI we preserve only the npm cache folder between jobs and not the unpacked node_modules. With yarn it's even worse because even when it's already in node_modules and already built, yarn will rebuild it at every operation, even if you're just adding a completely unrelated package as a new dependency. I don't really want to use precompiled binaries, but it was convenient given the state of javascript package managers. There's also just a lot of compiler warning spam that makes CI logs even longer, so not seeing that was another nice side effect. |
Hey, seems that I am facing a related issue using appveyor. The build gets stuck trying to install this library. I tried with yarn and npm (latest versions) and with Node 8 and 9. I am also using electron-builder. Any ideas of what could be wrong?
image: Visual Studio 2017
platform:
- x64
# cache:
# - node_modules
# - '%USERPROFILE%\.electron'
init:
- git config --global core.autocrlf input
install:
- ps: Install-Product node 8 x64
- yarn
build_script:
- yarn release
test: off
|
secp256k1-node/appveyor.yml
Lines 5 to 10 in 2b1ed90
The text was updated successfully, but these errors were encountered: