Not latest version committed to npmjs about grunt-manifest HOT 11 CLOSED

Well we just lost a morning to this issue!

Please at least state in the README.md npm install grunt-manifest --save-dev will not install the version applicable to the following documentation.

from grunt-manifest.

Is there any reason you are not publishing the latest version to npm? It has a few features we need and we're are having to use a git url to depend on the latest version.

Also, +1 on getting burned by documentation not matching published version.

Let us know if there's anything we can do to help get the latest version published to npm.

from grunt-manifest.

Same here, would love to see latest version on npmjs... For what it's worth, wgetting the tasks/manifest.js file into my local node_modules/grunt-manifest/tasks seems to at least fix my immediate problem of the hash feature not working in the current version from npmjs.

from grunt-manifest.

A cleaner way is to use:

   "grunt-manifest": "git://github.com/gunta/grunt-manifest.git#0.4.2",

in you package.json

from grunt-manifest.

@gunta please respond :)

from grunt-manifest.

@gunta ?

from grunt-manifest.

@maboiteaspam I can't publish the new release to npm. Only a contributor for this git repository.

At least you can still follow the advice from @matthieusieben and using the tag.

from grunt-manifest.

Sorry for the big delay. Updated now.

from grunt-manifest.

Woo! Thanks.

from grunt-manifest.

@stephanebachelier yes, thanks, is it what i did in a short. Let s say it is preferable to rely on published npm package.

@gunta thank you !

from grunt-manifest.

@maboiteaspam we agree :)

from grunt-manifest.