Utilize npm private module to package shared library for different React / React Native clients. Shareable code goes here. Basically deliver Redux Store with Firebase integration and business logic in a library. Each React app utilizes this while delivering a device/target specific UI.

With Browserify we could create the inspector snippet used to connect the user's devices with the Dashboard. Using CommonJS modules we could organize large amounts of code alongside third-party JavaScript modules.

If you're using Node or Gulp, you can't help but use NPM in some form or another. Fortunately that's never a bad thing with the massive package repository and glowing ecosystem making it a breeze to work with.

It's the lesser of all of the other evils out there. Webpack makes you completely blind to how things are put together. I like gulp, this made it easy.

We manages all of our packages, including Angular JS through npm. It is a very quick way of downloading / installing packages into your project.

Module is published as bpost on the npm registry. Tasks for the module are also defined as npm run tasks with commit hooks for git

Used for project package management.

The Twit, .envs, and Clarifai packages are currently the major packages used for the bot

No real definitive reason, I find it to be the most natural way to import libraries and code in nodejs (prior to ES6 / import).

Used Require.js to make the application modular. It provides better dependency management with asynchronous loading of scripts.

The RequireJS package manager is used by various web applications and services to manage dependencies on 3rd party libraries.

Main React functionality pipeline broken into CommonJS modules: Reflux data stores, React components (cjsx - coffee/jsx).

Made sharing node modules with the frontend real easy. Especially when developing hybrid apps.

Very nice way to structure a project, as long as you know it will not be a hybrid app.

We use Browserify to keep our JS organized by requiring modules.