Hacker News Reader

Looks like the directory structure (in lib/...) is related to the use of component.io? [for app components].

I typically build node apps with application "modules" in an apps/{name} structure and then require them all in server.coffee.

Component.io is new to me, it claims to provide an entire "bundle" of client & server side pieces, this is nice. I'll have to look into that today ...

Definitely, an explanation of these "best practices" would be nice.

View on HN

I know that most people tend to organize their code with assets for client side assets, lib for code, test for all of their testing code and index.js as the root of the application. Including the node binaries in bin is also a nice touch. I just have never seen the component usage before and definitely need to look it up as well.

EDIT: The component todo example seems to use components on the client side but not the server side https://github.com/component/todo

Take a look at the branches it has. Also look at component.io website code. ;)

Reply on news.ycombinator.com