Integrate npm bootstrap-sass; Remove bootstrap-sass gem; Update README

[mbreining]

Justin, please review. Let's chat tomorrow.

[justin808]

We should mention https://github.com/justin808/react-webpack-rails-tutorial/blob/master/Procfile.dev

foreman start -f Procfile.dev

[justin808]

@mbreining Anything pending? or ready to merge?

[mbreining]

@justin808, take another look and see if you want to merge. Note that I have not addressed your offline comment on ExtractTextPlugin (add the webpack/assets directory to the asset pipeline config). We should talk.

[justin808]

I've changed my opinion on this based on a real project. Basically, my thought right now is:

1. Use rails gem bootstrap-sass, and configure the rails assets to include the webpack/assets directory
2. Use the bootstrap-sass-loader without the extract text plugin, so that hot reload works.
3. The final thing that's somewhat non-optimal is that the information on what bootstrap components will be loaded is duplicated for both the rails sass import as well as for the config file for the bootstrap sass loader. It's not that big of a deal, but I hate anytime there's duplicates.

There's a bug with the bootstrap-sass-loader in that it uses a full local path for the font directory. That's clearly a problem when publishing the CSS file for deployment.

Thus, I'd rather let the bootstrap-sass gem and the rails asset pipeline handle all those thorny issues of paths for fonts and images, as well as fingerprinting.

Throughts?

[justin808]

Here's the issue on the path being absolute: shakacode/bootstrap-sass-loader#3

[mbreining]

@justin808 please take another look. We can continue to iterate over time but this batch of changes should be ready to merge, pending your comments.

[justin808]

we will change this shortly, but this can be the next PR

[justin808]

I think we should remove the comments on the extract text plugin.

I think for rails deployments, it's just not worth any complexity to have webpack extract the files...

The reason that we'd want webpack to do it is b/c you want the file for the webpack dev server testing...For right now, I'm not convinced.

[justin808]

Looking great! getting close!

[mbreining]

Ok, I think all comments are addressed. Please review.