-
Notifications
You must be signed in to change notification settings - Fork 54
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
Install fails with github actions #12
Comments
That seems like a yarn issue, can you try npm? |
still not working 🤔 my ci config file is available here (if needed) : https://github.com/iwaQwQ/Q-Bot/blob/feature/ci-update/.github/workflows/ci.yml |
|
I'm still a newbie with Github Actions, so I may have made some dumb mistakes, sorry about that I put every needed dependencies into devDep because I run multiple bots on my server, so instead of having to install libsodium for each bot, i've installed it globally. |
Yeah, sadly thats not how things work in node. Every package.json should list all the things it needs, otherwise we cant guarantee working conditions on packages, like the issue you have right now |
Alrighty, thanks for the advice, I'll try again with the corrected list then |
Alright, I've fixed my dependencies list, but it was still not working The issue seems to be only on Github Actions, I tried to install the package on my mac (macOS 10.15.4) and my server, which runs on Debian 10, and everything worked well Anyway, thanks for your help c: I had another question, should I also install ffmpeg as a node dependency, or keeping it installed systemwide is fine ? |
Using
ffmpeg should be installed via the package manager of the distro you use whether that be |
yarn don't seems to have a similar option, so I think it only works with sudo rights when using yarn i'm closing the issue since it's fixed, thanks for your help! |
Please describe the problem you are having in as much detail as possible:
node-pre-gyp not found when installing the package on Github Actions
Include a reproducible code sample here, if possible:
Further details:
The text was updated successfully, but these errors were encountered: