-
Notifications
You must be signed in to change notification settings - Fork 14
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
Unable to install... #230
Comments
Can anybody shed some light on this issue, please? Been stuck here for a while now. |
Hello @conqueror8888, we are figuring out how to publish a couple of repositories that are actually hidden. The required source code will be released bit a bit under a submodule called "Network" on our "sdk" repository, therefore all As we are a small team, all our efforts are currently on improving the product, so, we can not ensure that all required changes for making this happen will be before Q3'. |
Appreciate your response. Any quick fix to allow the setup to complete at all? Or better wait for Q3 release? |
you need to use node up above 14.17 to install on 1/5 step but after that i encounter some issue, that Dependencies are missing or 404 not found
|
Attempting to install on Ubuntu 20.04 LTS and encountered the following:
root@apex:~/drive-server# yarn
yarn install v1.22.17
[1/5] Validating package.json...
error [email protected]: The engine "node" is incompatible with this module. Expected version ">=14.17". Got "10.24.1"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
root@apex:~/drive-server# node -v
v10.24.1
root@apex:~/drive-server# yarn upgrade
yarn upgrade v1.22.17
error An unexpected error occurred: "https://npm.pkg.github.com/@internxt%2finxt-js: npm package "inxt-js" does not exist under owner "internxt"".
info If you think this is a bug, please open a bug report with the information provided in "/root/drive-server/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/upgrade for documentation about this command.
yarn-error.log
yarn-error.log is attached here.
The text was updated successfully, but these errors were encountered: