Just a small question, is there a reason you are not tagging/releasing the repo? It can be really useful as it will mean others using it will be able to reference a specific version (to prevent any auto-update issues). My understanding is if you tag it on GitHub then people can do things like:
"grunt-harp": "~0.1.5"
To install specific versions or minor release changes but I don't see any releases listed on GitHub.
Ah, maybe npm doesn't read releases/tags? npm view grunt-harp versions seems to list the versions. Might be worth tagging them off on GitHub anyway for consistency?
Just a small question, is there a reason you are not tagging/releasing the repo? It can be really useful as it will mean others using it will be able to reference a specific version (to prevent any auto-update issues). My understanding is if you tag it on GitHub then people can do things like:
To install specific versions or minor release changes but I don't see any releases listed on GitHub.
Keep up the great work!