There is every reason to use package.json, because it is a place to list your npm dependencies so that they can be easily installed, and a place to list scripts that you use to start and test your software.
Now, hopefully that can be the end of this thread. I am not subscribed to this group in order to hear people bicker; I am here to learn interesting technical information about node, so I would appreciate it if we can confine our conversations to that. On Mar 27, 2014, at 22:58, Frank Z <[email protected]> wrote: > So as far as I'm concerned, from the documentation, there's no reason to use > a package.json unless you are submitting your module to NPM to be downloaded > by other people. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
