-
Notifications
You must be signed in to change notification settings - Fork 254
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
0.19.1 #519
Comments
I second this, the binaries aren't located on github, meaning nodegyp has to recompile everytime |
+1 Please tag the NPM release on Github for every npm version so that we can get the pre-built binaries. Going through the compilation takes WAYYY too long.... Thanks =) |
my problem is that for me it doesn't build on windows or linux, i dont remember, but all the others are building. thats why it is weird. |
+1 |
i use it like this, in package.json: |
then it will not try 0.19.1... and this is not done at right now for 0.19.1 |
@p3x-robot That's what I am also doing. Other versions still compile fine for me on Mac or Linux, but it is much slower than downloading the pre-built binaries available for specific versions |
Sorry about any inconvenience. I just drafted 0.19.2 for release. I tagged the version in GitHub releases, so once it builds I'll publish to NPM. |
it is verified in 0.19.3 is working. |
Hello!
How are you?
It is in npm already 0.19.1, but the bindings are not existing in the releases and it does not build natively on Linux.
I fixed it on the package.json to =0.19.0
Thanks very much!
patrik
The text was updated successfully, but these errors were encountered: