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
grpc issues - fails to build newIde on windows - if using Node Lts or current, instead of 8.x.x #989
Comments
this is the same as |
@4ian seeing as to how 10.15 is the lts release of nodejs now- this can potentially be a problem for other users to build GD, unless they specifically download nodejs 8 perhaps we should try to address this or make it clear in the readme that version 8 must be used Has anyone been able to build GD in nodejs 10.xx LTS ? Or latest? |
Can you try updating firebase to latest version in package.json, and npm install again with Node 10? |
doing that gets me further, but still fails to build first i get this warning:
then:
|
I confirm that downgrading to nodejs 8 fixes the issue, but version 8 is no longer LTS |
could try this |
Mmm I'd like to identify what's the package creating the issue. 🧐 We should not have to artificially add a new dependency without knowing why. |
This being said, it's true that everyone is telling about this. Let me know if it's better when you |
Issue seems to be with fstream that is using graceful-fs that is using some Node internals. We should see what is using fstream and if we can update this.
EDIT: unzip2 seems abandoned :/ Should switch to something else to unzip files. EDIT2: https://www.npmjs.com/package/unzipper seems better |
Can you pull master and retry? I've replaced unzip2 by unzipper, which comes with a newer version of fstream (v1) and graceful-fs (v4). Hopefully all of this is compatible with Node 10. |
@4ian I will try to build on 10 again tonight @Jose-Moreno are you sure you have enough disk space on C drive? The tarball warning indicates that it possibly fails to download the whole thing |
This indicates to me that the problem is more related to Node or your system than GDevelop. Not sure what's going on but this looks like permission/space disk issue.
Good thing to check indeed. |
it's worth deleting the node_modules folder between tries too :) |
Yeah, always always delete node_modules and re-run |
@4ian I had a try - still fails to build. Same reason :( Heres log:
Have you had an opportunity to try it with nodejs 10? If so, is it fixed on macOs? |
I tried installing natives@1.1.6, doesn't fix it either :) |
when trying to run it after the failed install, you get this
doesnt even start |
@blurymind @4ian Hi, thanks. Just to be clear I never said it's the fault of GDevelop, I explicitly said it's a problem with the GRPC 1.10.1 package, as well as the monaco tarball showing signs of corruption (says so in the images). I even mentioned that i tried to download each package individually, without GDevelop. For sure, It may even be a problem with npm for windows itself which is pulling corrupted tarballs for that specific distribution of monaco editor, but the fundamental problem is: no grpc, no GDevelop. Also, FYI , I deleted / cleaned the npm-cache / .staging folders between tries. In reply to your other comment, I am the administrator of my system, ran git-bash as admin and have over 120 GB left in the HD to download these packages, so i kind of doubt it's a problem with disk space 😕 Though I agree that this may be a very Windows specific problem with permissions (no surprise there to be honest 😩 ) however other packages download just fine, it's just the grpc that fails. That said, I'm not the only one that's been affected by this though, people on discord and on the grpc github repo have expressed similar problems, so this is an old problem it seems (I already tried their solutions but no luck). I personally just wanted to share the related issues in lieu of helping you find a solution, so apologies if my comment seemed unhelpful. I wish I could help more but this Node ecosystem is quite complex for the uninitiated. When I have some free time i'm willing to install each package individually if that's what it takes, I'll also have to try and use yarn instead of npm to see if that solves the problem. Thank you both for your replies and for testing this problem. Cheers. |
@blurymind @4ian Hey, I'm back. So, I tried working with Yarn and unfortunately I couldn't make it work as Yarn seems to have it's own set of unresolved bugs however thanks to that, I ended up deleting the existing locked files (package-lock.json + yarn.lock) that come in the newIDE folder when cloning the repo, and well suffice to say that everything worked now! 🎉 I installed the grpc package individually first and downloaded super fast, no issues. Then I proceeded to download the rest by using Afterwards I cleaned everything again and tried to install via npm but this time using the latest Node LTS (10.15.3) and well at least now I'm getting consistent errors with Todor:
I found a few related issues with this same error on github, but their solutions wouldn't work either even though it seems to be related to permissions. Lastly, I found that in older iterations of this problem some people seem to have fixed it by installing firebase which pulls grpc as a dependency. I've tried this with Node LTS 10.15.3 and it works! Although grpc is installed as a module inside the @ firebase folder, so i'm not sure if this is an actual workaround for this problem? What do you think? Will this let GDevelop build and work as expected if we do it like this? Edit: I noticed that even though I pulled the same version of firebase that GDevelop has on it's package.json the actual grpc version that appears as a dependency is 1.7.1 and not 1.10.1, so I guess this might not be a proper workaround either 😕 |
|
@4ian That's great to hear actually, now it's all clear. After doing a bit more research into firebase's json it seems that it's firestore that needs grpc:
What's bothering me now is that I tried just to remove the explicit grpc line from the package.json file to let firebase pull the required version by itself, and it's really odd that it keeps failing with the same grpc@1.10.1 error, even though the property is gone form the package.json file, but when pulling firebase@4.8.2 by itself it works and on it's own pulls grpc@1.7.1 and today it places the folder outside of @ firebase, and not inside like in the previous screenshot 😕 So now I have to install firebase first before running There's also a problem when i use |
Ok, so I was having some issues with webpack versions being higher for Once I did that, after all the problems I managed to run It seems the electron build also opened succesfully so I'll gladly plan to make a quick video guide with my experience for other people to workaround this issue without much difficulty, at least meanwhile there's a more definite solution. Thanks again for both of your input! |
I've (if I'm not mistaken) fixed compatibility with Node.js 10 by upgrading |
I'll test it out and let you know soon. Thanks for all the hard work! 😊 |
@4ian Excellent! the fix did for my environment. Now following the guide is enough to get both web and electron versions running, no more grpc issues! 🎉 @blurymind can you test it to see if it works for you as well? despite some audit warnings I managed to build with 10.15.3 LTS easily thanks to Florian's firebase upgrade. |
Good to know! Thanks for checking :) Should hopefully help more people run development versions of GD. |
since pulling the latest master, I've been having trouble building gdevelop's newide.
this error seems caused by firebase
I am on windows 10, tried reinstalling both versions of nodejs
(current and latest)
https://nodejs.org/en/
The text was updated successfully, but these errors were encountered: