it's for both. better say, it's for apps and libs. A Module is just a file in the Common.js style. there are many packages in npm that are both, lib and app (mostly CLI). so the right name is package, that is just: A folder containing a package.json file
Am Donnerstag, 7. März 2013 14:07:56 UTC+1 schrieb Justin Novack: > > Hello World! > > Is the npm registry for modules or applications? There's conflicting > words in the documentation. > > Long story short (too late!), upon seeing LIFX, and inspired by the NodeJS > Socket Lights video on Vimeo, I figured NodeJS would be a perfect minimal > app to control the lights. So, I have my first proof of concept working > with protocol buffers without the SDK being released, and I put it up on > npm (lifx.js) to both dip my feet in and encourage more development. > > But it's currently NOT a module you can call do to something, currently, > it's just an app. Eventually, I see it both as a front (app) and back > (module) end, but I'm not there yet. Am I executing poor form by putting > it up on npm? I am really just trying to get a feel for the community and > learn best practices. I'm only a week in, be gentle. > > Thank you for your consideration. > -- -- 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/groups/opt_out.
