Try out webpack. Webpack makes handling all of your assets into something trivial. I converted around 3,000 lines of Gulp files into a 200 line webpack config.

Try out webpack. Webpack makes handling all of your assets into something trivial. I converted around 3,000 lines of Gulp files into a 200 line webpack config. (Most of which ended up being alises, and this is a reasonably big project.) For an example of what makes it so awesome: var img = require('./foo.png') // "/output-path/0dcbbaa701328a3c262cfd45869e351f.png" Webpack will copy this file (foo.png) to your output folder, and rename it using the file hash, so it does cache-busting. You don't need to use other build tools, you can just use the webpack CLI. I personally use npm scripts. Webpack also allows you to setup aliases for modules, as well as load pretty much anything you can imagine. You wanna pull in a module that doesn't use CommonJS and instead exports a global? Webpack has global-loader. AMD is supported as well. Oh, and this includes a sane development environment, with reload on save, as well as hot loading assets that support it. (Check out react-hot-loader: http://gaearon.github.io/react-hot-loader/ http://gaearon.github.io/react-hot-loader/, but it works with css as well.) And you can require css files in your components, and then add the extract-text-webpack-plugin so it'll rip the css from the generated JS bundle! Aaaaand it handles SourceMaps, so you don't have to worry about some plugins (looking at you gulp) not playing well together. Finally, it also handles minification, either through a CLI option or in the config.