Show HN: Command line task management tool (Weekend Project)

Nice work. Btw, I don't think you need to add node_modules to your repo, at least colors is already on npmjs.org and you can use package.json and NPM to distribute node.js 'env' enabled binaries, it should ease the configuration instructions. Hope this helps :)

Re: Show HN: Command line task management tool (Weekend Project)

#7

Post by importMe » Mon, Feb 18, 2013, 12:40 AM UTC

thepumpkin1979 wrote: post #6

Nice work. Btw, I don't think you need to add node_modules to your repo, at least colors is already on npmjs.org and you can use package.json and NPM to distribute node.js 'env' enabled binaries, it should ease the configuration instructions. Hope this helps :)

Thank you. I have just started with node, so your advice is valuable. Do you know if files with '#!/bin/node' (or was it '#!/bin/env/node') work in windows when published through npm?

Re: Show HN: Command line task management tool (Weekend Project)

#8

Post by niggler » Mon, Feb 18, 2013, 1:42 AM UTC

importMe wrote: post #7

thepumpkin1979 wrote: post #6

Nice work. Btw, I don't think you need to add node_modules to your repo, at least colors is already on npmjs.org and you can use package.json and NPM to distribute node.js 'env' enabled binaries, it should ease the configuration instructions. Hope this helps :)

Thank you. I have just started with node, so your advice is valuable. Do you know if files with '#!/bin/node' (or was it '#!/bin/env/node') work in windows when published through npm?

I haven't tried in windows, but the recommended way to handle binaries is through the `bin` field in package.json (and this technique doesn't care about the shebang because it doesn't run the script directly using the OS). For example, in the `xlsx` module:

"bin": { "xlsx2csv": "./bin/xlsx2csv.njs" },

https://github.com/Niggler/js-xlsx/blob/master/package.json#...

Relevant doc: https://npmjs.org/doc/json.html#bin

Re: Show HN: Command line task management tool (Weekend Project)

#9

Post by importMe » Mon, Feb 18, 2013, 1:55 AM UTC

niggler wrote: post #8

importMe wrote: post #7

Earlier quoted context omitted.

Thank you. I have just started with node, so your advice is valuable. Do you know if files with '#!/bin/node' (or was it '#!/bin/env/node') work in windows when published through npm?

I haven't tried in windows, but the recommended way to handle binaries is through the `bin` field in package.json (and this technique doesn't care about the shebang because it doesn't run the script directly using the OS). For example, in the `xlsx` module: "bin": { "xlsx2csv": "./bin/xlsx2csv.njs" }, https://github.com/Niggler/js-xlsx/blob/master/package.json#... Relevant doc: https://npmjs.org/doc/json.html#bin

Thanks, I'll take a look at that.

Re: Show HN: Command line task management tool (Weekend Project)

#10

Post by kodablah » Mon, Feb 18, 2013, 2:07 AM UTC

importMe wrote: post #7

thepumpkin1979 wrote: post #6

Nice work. Btw, I don't think you need to add node_modules to your repo, at least colors is already on npmjs.org and you can use package.json and NPM to distribute node.js 'env' enabled binaries, it should ease the configuration instructions. Hope this helps :)

Thank you. I have just started with node, so your advice is valuable. Do you know if files with '#!/bin/node' (or was it '#!/bin/env/node') work in windows when published through npm?

If you specify a js file as an executable file in your package.json, npm wraps it in a .cmd file on Windows just like it wraps it in a shell file on nix.