Echo JS 0.11.0

Hmm interesting why is using browserify usage equate to "hacky way" ?

Since browserify is taking npm modules and making them compatible on the browser.  As the article points out, you will only know if it works when you try and either fail or succeed.  And as the article comments point out, you would then need to make node_modules public or have something/someone in place to copy the files over to the public dir and keep them in sync.

NPM is great and so is browserify, but I just can't comprehend the idea of basing your front-end module system around something that confused about its own identity.

I use NPM w/browserify without any issues, when im on npm majority of the time module i am looking for states if it will work in browser or not...

For front-end development i symlink some modules into node_modules folder to make it cleaner to require them, instead have relative path hell ie '../../../'

Instead of using bower, or something similar i use napa (npm module), which lets me download something like foundation, right from github and put into my node_modules folder to use in my projects

Personally I like have one system to handle both my server scripting and my front-end as well.

I use NPM w/browserify without any issues, when im on npm majority of the time module i am looking for states if it will work in browser or not...

For front-end development i symlink some modules into node_modules folder to make it cleaner to require them, instead have relative path hell ie '../../../'

Instead of using bower, or something similar i use napa (npm module), which lets me download something like foundation, right from github and put into my node_modules folder to use in my projects

Personally I like have one system to handle both my server scripting and my front-end as well.

If it works for you then awesome.  I just don't like how it feels personally.  Also we don't use node on our backend where I work, that may account for my thoughts on the matter.