webpacker can also manage non-JS assets [ci skip]

Not sure if the whole paragraph in the README should go away, but after rails#153 it's not true that webpacker is _only_meant for JS files.
claudiob · Apr 10, 2017 · 106cfb3 · 106cfb3
1 parent 7b83822
commit 106cfb3
Showing 1 changed file with 1 addition and 3 deletions.
diff --git a/README.md b/README.md
@@ -4,9 +4,7 @@
 [![Gem](https://img.shields.io/gem/v/webpacker.svg)](https://github.com/rails/webpacker)
 
 Webpacker makes it easy to use the JavaScript preprocessor and bundler [Webpack](https://webpack.github.io)
-to manage application-like JavaScript in Rails. It coexists with the asset pipeline,
-as the purpose is only to use Webpack for app-like JavaScript, not images, css, or
-even JavaScript Sprinkles (that all continues to live in app/assets).
+to manage application-like JavaScript in Rails. It can coexist with the asset pipeline.
 
 It's designed to work with Rails 5.1+ and makes use of the [Yarn](https://yarnpkg.com) dependency management
 that's been made default from that version forward.