Project status?

[piranna]

At NodeOS we are looking for a git command written in Javascript so we can be able to install GitHub-based npm modules. Is this one working production grade, or does it need some tune-up? Would you like to contribute to our project? :-)

[whyleee]

Hi @piranna. I doesn't support this tool anymore, because I stopped using it a year or two ago. It was created for the same needs as yours, so the tool has exactly the required minimum features to support commands requested by bower and npm. We used it to restore npm and bower packages on the cloud build server, where we didn't have access to install local git.

I'm not a JS developer, neither well experienced in Node.js or git internals, so you will find the code is pretty basic. It was tested by me only on Windows mostly with grunt and other front-end build related packages on several projects. The last version 0.1 was tested with Node.js 4.0 and npm 2/3 versions.

It is based on js-git library and I found it is pretty raw, low-level and not well documented. I spent a lot of hours just trying to understand how can I start, what should I do, add missing functionality and fix different issues. My implementations of git commands are very basic and sometimes contain simple workarounds to escape additional complexity, so there is a chance it will break in some specific cases which I haven't tested. Another problem is that commands which are used by npm were changing over time and I need to update the tool for that. So maybe latest npm versions released this year already have new not implemented command calls, I haven't tested that.

I'm not sure I'm going to continue to work on this tool, as I'm not using it anymore and I'm busy digging into a lot of new stuff released lately in .NET 😃. But of course I'll help with any questions related to the tool or the code.

[piranna]

Hi @piranna. I doesn't support this tool anymore, because I stopped using it a year or two ago. It was created for the same needs as yours, so the tool has exactly the required minimum features to support commands requested by bower and npm

That's great! :-D

I'm not a JS developer, neither well experienced in Node.js or git internals, so you will find the code is pretty basic. It was tested by me only on Windows mostly with grunt and other front-end build related packages on several projects. The last version 0.1 was tested with Node.js 4.0 and npm 2/3 versions.

These are somewhat recent versions, and being basic is a plus because it would make it easier to integrate in the future in npm itself, so I don't find it a problem. Also Windows is usally the most problematic platform, so if it works fine there then it's a good sign ;-) We are only interested at the moment on the basic features needed by npm, so it's just enough.

It is based on js-git library and I found it is pretty raw, low-level and not well documented. I spent a lot of hours just trying to understand how can I start, what should I do, add missing functionality and fix different issues

@creationix, the author or js-git, is also aware of our willing to create a git cli for NodeOS, so if we have some problems with that probably he'll be easy to reach for help :-)

Another problem is that commands which are used by npm were changing over time and I need to update the tool for that. So maybe latest npm versions released this year already have new not implemented command calls, I haven't tested that.

Yes, that would be a problem... only solution here is to add first some good unit tests to prevent regressions.

I'm not sure I'm going to continue to work on this tool, as I'm not using it anymore and I'm busy digging into a lot of new stuff released lately in .NET . But of course I'll help with any questions related to the tool or the code.

It's a shame that you don't support it anymore, but maybe we could move it to NodeOS organization or do a fork there and maintain it there, and I could be able to add you as contributor if you want to work on it, what do you think? :-)