-
Notifications
You must be signed in to change notification settings - Fork 652
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
Fails to build with node.js v12.0.0 release #834
Comments
Same issue on Ubuntu 19.04, node 12.0.0 installed with nvm, grpc 1.18.0. |
This disables the travis build for the current Node.js version (12.0.0) until all dependencies support it. See: grpc/grpc-node#834
We are working on getting 1.20.1 out with node 12 support, stay tuned. |
|
Update: we had to unpublish 1.20.1 because it broke the TypeScript types. 1.20.2 will be out soon. |
I have the next issue with nodejs 12.0 when it runs npm rebuild, is it the same issue?
|
@aaaguirrep you haven't provided nearly enough information for us to tell if that's the case, but it most likely is, since it's 100% impossible to use grpc with node 12 at the moment. |
version 1.20.2 is now out. |
What is the process to upgrade gprc? I not see the new release in the repositorie. |
|
It worked, I dont see errors running |
Closing as resolved. |
does it work for yarn? I am having an issue upgrading or installing the new release but i am not sure if the issue is with grpc or other dependencies. |
Our yarn support always has been best effort. We don't officially support it. |
FYI this is used in FireBase and they still ship the old version that does not work w/ Node v12. |
I would suggest filling an issue with firebase then. |
I would love to - but I don't know how/where. I went on their website and filed a comment and sent a message to their group. The stack trace shows that the version they released TODAY is using the older version of grpc. I use 40 npm modules at least 10 are native and the only one w/ that does not work is Google Firebase. And no way to flag them or do PR. |
THANK YOU. |
I am also using firebase in my project and it shows the issue. I thought that issue was related to yarn. |
@aaaguirrep please upvote firebase/firebase-js-sdk#1738 |
npm ERR! grpc@1.20.0 install: I'm trying to use ( npm install ) to install a project node_modules |
Same issue: npm ERR! code ELIFECYCLE npm -v |
Please post the entire error message, or at least the first several lines. |
This issue seemed to be closed so opened #922 |
node-pre-gyp WARN Using request for node-pre-gyp https download npm ERR! code ELIFECYCLE |
Dear Grpc/Grpc-Node Team,
Sorry for the late reply. I have commented with the full error text from
the very beginning.
If you need info about my system or any other info just let me know.
Thanks in advance and I am looking forward to hearing from you.
Best Regards,
*Ahmed Mohammed Shehatah*
Front-End Web Developer
Email: engahmedshehatah@gmail.com
Mobile: +201005363688
…On Thu, Jun 20, 2019 at 7:22 PM pointer2null ***@***.***> wrote:
This issue seemed to be closed so opened #922
<#922>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#834?email_source=notifications&email_token=AJNQHEFQZVD5YOI76U6KJVLP3O4GXA5CNFSM4HH6ZQ22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYGCERQ#issuecomment-504111686>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJNQHEAROTBQUCPCF5GICIDP3O4GXANCNFSM4HH6ZQ2Q>
.
|
You are using a version of the grpc library that does not support Node 12. Please use either a newer version of grpc or an older version of Node. |
Same issue. |
i just downgrade node (10.9.0), and fixed for now. |
how you solve it |
see #922 for workaround |
Thanks it's working |
can you tell me the command to list all development environment ? |
Firebase js client appears to have a dependency problem grpc/grpc-node#834 Firebase issue tracker is a bit quiet about it, but installing grpc by hand might work.
Problem description
Reproduction steps
Environment
Additional context
Attached log files
2019-04-23T22_09_12_791Z-debug.log
console.log
The text was updated successfully, but these errors were encountered: