When creating a string for manual entry people often get confused by these. Best to not include them at all.

It is much better form to ship compiled coffeescript code in lib and src in source. You can do something like this:

"scripts": {
"test": "NODE_ENV=test node_modules/.bin/vows --spec spec/*-spec.coffee",
"watch" : "node_modules/.bin/coffee -c -w -o lib src"
},

in your package json and develop with
npm run-script watch

In addition this allows you to make "coffee-script": "1.2.x" a dev dependency only,

Something like this works well for me:

Publish new version

• Change version in package.json
• git tag -a v0.0.6 -m 'version 0.0.6'
• git push --tags
• npm publish

Also, to avoid errors, use the pkginfo npm and add this to your main entry point:

require('pkginfo')(module,'version')

it automatically exposes the correct version from within your lib

"homepage": "git://github.com/drd0rk/strgen"
should be

"homepage": "https://github.com/drd0rk/strgen"

Sorry, no time to fork...

As you are learning github, here is another best practice. Add your site to travis-ci.org, and add a build status link to your readme.