-
Notifications
You must be signed in to change notification settings - Fork 31
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
Must have git installed to download t2 cli #136
Comments
Why is it a prerequisite? |
I believe |
Makes sense. Thanks for clarifying! 👍 |
Why is there a special npmlog at all? Sorry if this is a known thing already, just seems weird. |
There wouldn't be if anyone at npm would follow on this: npm/npmlog#34 npm/npmlog#31
Yes. Please help me get the attention of someone at npm |
@rwaldron I know you have strong feelings about not polluting the npm ecosystem and I don't disagree one bit, but in this case would it be worth it for T2 users to go ahead and publish your version? I know most early adopters will of course have git, but with people ordering the J5IK and T2's figuring into Nodebots Day there are going to be people who are not git users coming into our community. The readme could be updated to read something along the lines of:
Similar problem getting a merge here: npm/fstream#16 Note the date that this PR was submitted |
To be fair, it looks like some work is being done on the fstream PR. |
@dtex yes, I think you're right. I will do exactly as you've suggested. |
This can be closed, there is no git dep in the coming release |
Closing this as fixed by @rwaldron with tessel/t2-cli@ee98070 |
@HipsterBrown thank you! |
We should note this prerequisite
The text was updated successfully, but these errors were encountered: