grunt-rev not published in npm

sebdeckers / grunt-rev

:punch: Asset revving for Grunt.js

MIT License

240 stars 54 forks source link

grunt-rev not published in npm #1

Closed sebv closed 11 years ago

sebdeckers commented 11 years ago

Working on publishing a patch for it to yeoman-generator.@sebv You're part of that project? Should I publish this repo to npm first or not?

sebv commented 11 years ago

Am not part of yeoman, but I know the code pretty well (old version).

Yes publish first it doesn't matter. You can bump the the version and update after you publish.

sebdeckers commented 11 years ago

Published: https://npmjs.org/package/grunt-rev

Few questions about publishing to NPM though, maybe you can clarify:

Do I need to create tags or branches for each "version" of the package in NPM/Grunt?
Does the Revision History of the README.md file get automatically created or is it manually maintained by every Grunt plugin author?

sebv commented 11 years ago

No need to create branch version or tag, I think npm uses build number. If there is a major upgrade or special case then you may, but best to keep it simple until you get used to npm.

When there is a new version you just need to bump the version in package.json and run npm publish again. If you want to update npm without changing version number you can run npm publish --force

As far as I know, the revision list is manually created.

sebdeckers commented 11 years ago

Thank you :heart: