npm install fails when installing repo dependencies for development
#20370
Comments
|
Hey @alt-glitch I just tried a clean install following the guide and everythings working. Can you try deleting node_modules and doing a clean install with Also make sure your package-lock file doesn't have any changes. LMK how it goes! |
|
Hey @jordienr I think the error is that;
Let me know if I might be missing some dependencies on my system. I found the following issue launchql/libpg-query-node#25. I went and tried to build I will try to see what the issue is with my system, though it's peculiar that my ubuntu box behaves the same. |
|
Hey @jordienr, |
|
hey there, the 404 may be a separate issue but the build you are trying needs the 'make' command. Which box are you running this on? Adding 'make' to the installed packages should address this, can you try that? |
|
Hey @encima Does my postgres version make a difference? Screenshots below: |
|
it shouldn't make a difference (unless it wasn't install at all) but the fact you can make v16 is interesting. |
|
Hi there,
Running Are the machines |
|
Hey @encima! Installing libpg_query fails when glibc=2.38 due Issue should be solved if the pre-compiled binary is available I think. cc: @iharshspatel: can you check your glibc version using Edit: I'm interested in helping out solving this issue, want to contribute to Supabase! Maybe I can |
|
This issue still exists. |
|
@ameerhazarika To confirm it is a windows only bug, can you try installing using WSL and report back please? |
|
@encima Hey. I'm afraid I cannot use WSL since there's a BIOS password in my system. I'm not able to access the BIOS settings to enable virtualization. |
|
I'm still working to resolve this whether or not it's a Windows issue. Will update if I find anything. |
|
@encima Hey. I tried running this on another system with Kali Linux installed. Followed all the steps as mentioned in the supabase documentation, and I was able to successfully setup the local development environment for Supabase on my system. |
|
@encima I think this issue is already being discussed for a long time now. |
|
Thank you for the efforts you put in here! It does indeed seem to be Windows only. If this is ok with you, I would close this issue to track supabase/postgres-meta#387 as the source? I will check this internally with the team in case there is any new info.. |
|
Hey @encima |
|
Noted, yep, and thanks for the offer of help! |
Yes, no issues. You can close it , but it seems @alt-glitch still has an issue on his system so there's that. Let me know if there are any updates from the team on this so we can help resolve it. Thank you |
|
I confirm the issue on my side, using latest Fedora Linux: ../node_modules/.pnpm/libpg-query@15.0.2/node_modules/libpg-query: Running install script, failed in 25.9s
.../node_modules/libpg-query install$ node-pre-gyp install --fallback-to-build
│ node-pre-gyp info it worked if it ends with ok
│ node-pre-gyp info using node-pre-gyp@1.0.11
│ node-pre-gyp info using node@20.11.0 | linux | x64
│ node-pre-gyp info check checked for "/home/XXXXXXXXX/xxxxxx/xxxxxxxxxxxxxx/node_modules/.pnpm/libpg-query@15.0.2/node_modules/libpg-query/build/Release/queryparser.node" (not found)
│ node-pre-gyp http GET https://supabase-public-artifacts-bucket.s3.amazonaws.com/libpg-query-node/queryparser-v15.0.2-node-v115-linux-x64.tar.gz
│ node-pre-gyp ERR! install response status 404 Not Found on https://supabase-public-artifacts-bucket.s3.amazonaws.com/libpg-query-node/queryparser-v15.0.2-node-v115-linux-x64.tar.gz
│ node-pre-gyp WARN Pre-built binaries not installable for libpg-query@15.0.2 and node@20.11.0 (node-v115 ABI, glibc) (falling back to source compile with node-gyp)
│ node-pre-gyp WARN Hit error response status 404 Not Found on https://supabase-public-artifacts-bucket.s3.amazonaws.com/libpg-query-node/queryparser-v15.0.2-node-v115-linux-x64.tar.gz
│ gyp info it worked if it ends with ok
│ gyp info using node-gyp@8.4.1
│ gyp info using node@20.11.0 | linux | x64
│ gyp info ok
│ gyp info it worked if it ends with ok
│ gyp info using node-gyp@8.4.1
│ gyp info using node@20.11.0 | linux | x64
│ gyp info find Python using Python version 3.12.1 found at "/usr/bin/python3"The issue happens when I run |
|
I tried following the instructions provided at the following link, and it still fails: https://github.com/supabase/supabase/blob/master/DEVELOPERS.md In my case, on my Windows 10, here are the error messages I am getting: |
|
Hello all, This is an issue with an external dependency. As some have noted, you can build this yourself for the system you run. An alternative is to run the Supabase stack using the supabase CLI or using the |
|
I wanted to run the repo locally so I can contribute. |
|
This might have been fixed by this PR #26618, which updates all |
|
so far i tried this on a fresh ubuntu and nixos machines .. please someone tell me if there is a work around |
Bug report
Describe the bug
On running
npm installafter cloning the repository, it fails with the following log (some parts trimmed) :To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
System information
Additional context
Seems to me that @gregnr/libpg-query package isn't building properly. I also notice that this URL: https://supabase-public-artifacts-bucket.s3.amazonaws.com/libpg-query-node/queryparser-v13.4.0-dev.12-node-v108-linux-x64.tar.gz is returning a 404.
Do let me know if I can give more information about my systems. I've tried and tested this both on my local machine and Ubuntu box.
Thanks!
The text was updated successfully, but these errors were encountered: