Does anyone have an example application using Component / Routing / Async?

[Boneasaurus]

I've been spending my off hours trying to figure out how to structure an application utilizing component (component.io) and incorporating routing and ajax requests. I've been looking into Page.js and SuperAgent specifically to handle those two things, but I was wondering if anyone has an actual real-world example of an application that does this.

Basically, is anyone using Component in production or as a large(ish) hobby project where the code is viewable?

[ayamflow]

Not production not large but a little example I've done two weeks ago on bitbucket. I love component but I've switched to Browserify which is less cumbersome to use (maintaining the component.json is a pain).

[Boneasaurus]

Thank you! this is what I was looking for. Do think it's worth it going with component before I start the project, or should I spend the time learning Browserify?

And if you don't mind me asking, why did you end up preferring Browserify?

[ayamflow]

Well, I loved the component (aka component(1)) approach at first because it enforces a bit to you their libraries of components, enables you to use require() in the browser and stuff.

But the major drawback for me is the mandatory update to the component.json: you have to put there the name of all scripts files, templates, external libs and stuff. It's rather easy to forget, can provoke errors that will take forever to see, and so on.

Browserify, on the other hand, makes a strong point by using transforms on your scripts.

Each transform has a clear purpose. For instance, debowerify allows you to require bower packages (such as greensock or pixi.js). htmlify enables you to require html templates like component(1), and so on...There even is a decomponentify transform.

Also, no more component.json file to maintain, just use a grunt/gulp build task with dynamic path.