-
Notifications
You must be signed in to change notification settings - Fork 302
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
Ensure solid-server works when installed globally with npm #685
Comments
Are there any tests which are run automatically ? |
Yes, but only library tests, no tests that cover the executable.
|
Running into an issue when doing a clean global install on ubuntu. $ sudo npm install -g solid-server npm ERR! A complete log of this run can be found in: |
Seems like that specific issue would be solved in develop, as that version no longer depends on a package from GitHub (and it shouldn't). @kjetilk Shall we release a new patch version? |
Yeah, lets do a patch version! Lets find a time for you to walk me through the release process. |
Okay, ping me tomorrow afternoon! |
let me know once it's pushed and i'll confirm the fix 👍 |
@justinwb Published, please test :-) There might be other blockers ahead, but not the git ones. |
This is still happening to me, but i believe that i tracked down the root cause, identified in this issue: zkat/pacote#105 I can confirm that when i run the global install as sudo, i get the error error time. However, if I su to root rather than 'sudo -s' or running the command as sudo, the install works correctly. |
The exact same error? Because the dependency on a git repository should be gone. They mention npm 5.x there. Does it also happen if you |
It was almost exactly the same, although i noticed the flags getting passed to git were slightly different. I should've grabbed them and pasted back in, but I can reproduce exactly later tonight. I was at least able to get around it by su'ing so I'm not blocked, but I'd still consider this a blocking issue since we recommend global install and 99% of people will do that via sudo because they're using cloud instances. I will test with latest npm tonight. |
Yeah the |
Hmmm, this seems like something we should have fixed soon, but are we effectively blocked by the upstream issue? |
As some added context for this, here's a log demonstrating the issue exactly with a clean install, as well as testing LTS and latest version of npm. Note that switching from sudo to straight su works at the end...
|
There's a PR upstream now, if anyone wants to try it out. |
Not sure if it's some incorrect config on my part, but I haven't had luck with global install:
|
Can confirm that this problem has been resolved in release v4.1.2-rc.0 (ae99c39)...
@cory2067 - While your issue was not specifically the same as the issue reported here, the fix was, and you should no longer be running into this anymore either with the latest release (v4.1.2-rc.0) |
There are reports of the solid-server executable not working when installed globally. It's rather important that it does, however, or we essentially have a broken npm package.
While this is hard to test on Travis, Solid developers could always run the global executable:
The text was updated successfully, but these errors were encountered: