-
Notifications
You must be signed in to change notification settings - Fork 30
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 git vs https #231
Comments
Yes, https should be fine for folks who are just downloading a read-only copy of the repo. Please test that changing it to https fixes your issue, and PR if so. |
@scottleibrand thanks, will test and let you know, then hopefully PR. Likely to be next week. |
@scottleibrand sadly this didn't work and appears to be a know issue with The issue appears in line 10. Line 10 in 900f631
Observed point is immediately after
So I tried adding
Any ideas if i'm missing some single quotes? The manual work around still works https://github.com/xdrip-js/Logger#install-issues. Thanks. |
I'm not familiar with that url insteadOf thing. Do we need to revert anything? |
I'm not familar with it either, just tried it and it worked.. Nothing to do at the moment. Will keep thinking about it as i look as some other bits. Thanks |
Cloning into 'xerosploit'... |
Hi,
Regarding install url for logger and the issue i've had previously.
Is there any benefit in using git instead of https?
Logger/package.json
Line 17 in 5912b7b
My install fails, i believe, due to this one and only instance of "git" in the code hence why i had to find a work around previously and additional comment in the troubleshooting help.
Also i notice that Oref0 uses "https" for the repo location in the package.json, https://github.com/openaps/oref0/blob/acb0150021e7bf284b6741a9510076a13f690747/package.json#L11.
I propose that we change package.json line 17 to be
"url": "https://github.com/xdrip-js/Logger.git"
I'm happy to make the pull request just unsure why it's git// in the first place.
thanks,
The text was updated successfully, but these errors were encountered: