On Apr 22, 02014, at 13:34, Chetan Dhembre <[email protected]> wrote:
> Most of time node_modules folder is added in .gitignore > You could not do that ;-) Seems the simplest solution. > .. and adding these local module in node_modules after making. Chages is > painful.. thats way i created the module .. btw i know it is not ideal > solution.. ideal scenario should not create nested directory structure.. I think nesting is good — but I try hard to keep nesting modular, rather than arbitrary. You won’t find much “js/”, “css/”, “images/” in my projects for this reason, but you might find “login/”, “billing/”, etc. — they’re modules that talk mostly or entirely to themselves. > just in search of some good blog post which will explain it with fairly > complex problem .. or about how to organize code in node.js project I think part of the problem is that there’s no canonical node.js project: Several frameworks have some rough ideas about structure, but node is more general. If you want good advice on how to organize, you might have to be a lot more specific. Node’s not just for the web, you know! Aria
signature.asc
Description: Message signed with OpenPGP using GPGMail
