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.
Ok you got me on the wording there, it was more of a question to gain insight to what other people are missing from browserify that say webpack provides. To me, and I have had this conversation with multiple people and substack himself mentions it below, browserify itself or via third party support does everything i need and can do a lot of what webpack does, so again I was looking out of curiosity what I am missing.