Distribute on NPM?

[MeirionHughes]

It might be nice to be able to run gitversion in Node and then from there we can have gulp-gitversion.

[JakeGinnivan]

That would be cool. I am thinking we hold off for v4 to do this, because then we will have cross platform support via mono.

[gep13]

I have never done any npm packaging, is this something that is simple to do?

[MeirionHughes]

@JakeGinnivan fair enough. :)
@gep13 I believe so, a few lines in a build script when its setup. end-users then just need to install node.js (or just npm on its own) then it would be as simple as npm install gitversion -g to use it computer wide, or locally in a single project. Beauty of it is its exactly the same usage on Windows/Linux/OSX

[gep13]

@MeirionHughes what about the gulp-gitversion portion? Is this something that we would want to take ownership of?

[JakeGinnivan]

I think we should take ownership of it, to be honest there is little friction in maintaining it. There is a lot more when someone else has to play catch up all the time. Once appveyor allows us to have command line deployment tasks then I can automate NPM, Gulp and Ruby deployments

[MeirionHughes]

gulp-gitversion would basically be a wrapper around gitversion with the src being the folder (?), plus a json parse and version selector. Once its setup I don't think you'll look at it again.

Edit; thinking about it. May well not need a gulp task anyway unless you do something special.

[gep13]

I think we should take ownership of it,

Yip, I was thinking the same, just wanted to make sure we are on the same page 😛

[JakeGinnivan]

FYI just looking at this, I would simply be creating a lightweight NPM package with a node api. I dont see us creating a gulp package, if you are using gulp you can still call node APIs and there are plenty of bridge projects.

Personally I just use NPM scripts

[MeirionHughes]

Fair enough, its easy enough to run your own code in a gulp task anyway.

To implement this, it might be easily done by simply calling the .net library/executable via https://github.com/tjanczuk/edge

[dazinator]

Being able to execute gitversion as a gulp task, could tie in to #647 - i.e you could update the project.json file also. Debatable whether gitversion would actually need to handle updating the project.json file itself, or whether we could just document a gulp task that pipes the git version supplied version number to another gulp tool to update the file..

[roryprimrose]

This would be great. I've just put together a SPA proof of concept that uses gulp. I want to create a nupkg of the gulp output to push to Octopus Deploy. Being able to update the version of the nuspec via GitVersion would be very handy.