npm-pipeline-rails 1.1.1 → 1.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 87487679b6a5d6d28e33ac1e5a5159c196d4a7bb
-  data.tar.gz: 217798c9d06c247379afa503fd9564a9841c8539
+  metadata.gz: 33f1c5e32f28a8965aa36c2d1ce2cec54a3b22c3
+  data.tar.gz: 75670cfba6475b6b21419611ff6857f838562810
 SHA512:
-  metadata.gz: d08900a5c70f9f8d3ef96a26adcba6708ffb631669fc0b730a7b64578dd87dcfda16fc01955f5f2ca3bc7344ec2cc3d91f4eb093f04a963c6ebdf2314469673c
-  data.tar.gz: 256921cb8f32fd7081fc6396f9d17fcd61b88942e57b1f3eee317ed3e8fa3e9aa04f8837ae61ffd85fc48601d62cbce424f7fac6134378fcf09e54ba9e497c44
+  metadata.gz: 4e778eaaaaaf92b9a3252f5e07b89719c40089c8540fed1f116940e4760c6b227d27cea3d81c7d6f8f7ac7a4033af3ad7b49c06cf42568a1a76419ca3a50e9fc
+  data.tar.gz: b52b034e540931e69619cabd59a0986b9a31c1853d09e6de05c2a862dea72fb39b7f767b9e6f61ef3610d765accf401bf43a23e0a70b6857ec6d34d57cd960b6

data/HISTORY.md

@@ -1,3 +1,10 @@
+## [v1.1.2]
+> Mar 22, 2016
+
+- Make the gem package smaller; no functional changes.
+
+[v1.1.2]: https://github.com/rstacruz/npm-pipeline-rails/compare/v1.1.1...v1.1.2
+
 ## [v1.1.1]
 > Mar 22, 2016
 

data/lib/npm-pipeline-rails/version.rb

@@ -1,3 +1,3 @@
 module NpmPipelineRails
-  VERSION = '1.1.1'
+  VERSION = '1.1.2'
 end

data/npm-pipeline-rails.gemspec

@@ -14,7 +14,7 @@ Gem::Specification.new do |spec|
   spec.homepage      = 'https://github.com/rstacruz/npm-pipeline-rails'
   spec.license       = 'MIT'
 
-  spec.files         = `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(examples|test|spec|features)/}) }
+  spec.files         = `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(docs|examples|test|spec|features)/}) }
   spec.bindir        = 'exe'
   spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
   spec.require_paths = ['lib']

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: npm-pipeline-rails
 version: !ruby/object:Gem::Version
-  version: 1.1.1
+  version: 1.1.2
 platform: ruby
 authors:
 - Rico Sta. Cruz
@@ -106,12 +106,6 @@ files:
 - Gemfile
 - HISTORY.md
 - README.md
-- docs/brunch.md
-- docs/gulp.md
-- docs/motivation.md
-- docs/screenshots/build.png
-- docs/screenshots/full.png
-- docs/screenshots/server.png
 - lib/generators/npm_pipeline/brunch/brunch-config.js
 - lib/generators/npm_pipeline/brunch/package.json
 - lib/generators/npm_pipeline/brunch_generator.rb

data/docs/brunch.md

@@ -1,67 +0,0 @@
-# Brunch integration
-
-Run this to set your project up with a simple Brunch config.
-
-```sh
-./bin/rails generate npm_pipeline:brunch
-```
-
-## Manual setup
-
-If you don't want to use the generator, here's what it does.
-
-#### package.json
-
-> Set it up with `brunch` and some basic plugins.
-
-_See:_ [sample package.json](../lib/generators/npm_pipeline/brunch/package.json)
-
-#### brunch-config.js
-
-> Set it up to watch source files in `app/brunch`, then put built files into `vendor/assets`.
-
-_See:_ [sample brunch-config.js](../lib/generators/npm_pipeline/brunch/brunch-config.js)
-
-#### .gitignore
-
-> Set it up to ignore Brunch's built files.
-
-```
-/node_modules
-/vendor/assets/stylesheets/brunch
-/vendor/assets/javascripts/brunch
-```
-
-#### app/assets/stylesheets/application.css
-
-> Set it up to include Brunch's built files. This will load from `vendor/assets/stylesheets/brunch/app.css`, as built by Brunch.
-
-```css
-/*
- *= require brunch/app
- */
-```
-
-#### app/assets/javascripts/application.js
-
-> Set it up to include Brunch's built files. This will load from `vendor/assets/javascripts/brunch/app.js`, as built by Brunch.
-
-```css
-//= require brunch/app
-```
-
-#### app/brunch/
-
-> Put your source files into `app/brunch`. For instance:
-
-* `app/brunch/example.css`
-
-  ```css
-  * { color: blue }
-  ```
-
-* `app/brunch/example.js`
-
-  ```js
-  alert('it works!')
-  ```

data/docs/gulp.md

@@ -1,67 +0,0 @@
-# Gulp integration
-
-Run this to set your project up with a simple Gulp config.
-
-```sh
-./bin/rails generate npm_pipeline:gulp
-```
-
-## Manual setup
-
-If you don't want to use the generator, here's what it does.
-
-#### package.json
-
-> Set up `gulp`, `gulp-cli`, and some basic Gulp plugins.
-
-_See:_ [sample package.json](../lib/generators/npm_pipeline/gulp/package.json)
-
-#### gulpfile.js
-
-> Set it up to watch source files in `app/gulp`, then put built files into `vendor/assets`.
-
-_See:_ [sample gulpfile.js](../lib/generators/npm_pipeline/gulp/gulpfile.js)
-
-#### .gitignore
-
-> Set it up to ignore Gulp's built files.
-
-```
-/node_modules
-/vendor/assets/stylesheets/gulp
-/vendor/assets/javascripts/gulp
-```
-
-#### app/assets/stylesheets/application.css
-
-> Set it up to include Gulp's built files. This will load from `vendor/assets/stylesheets/gulp/app.css`, as built by Gulp.
-
-```css
-/*
- *= require gulp/app
- */
-```
-
-#### app/assets/javascripts/application.js
-
-> Set it up to include Gulp's built files. This will load from `vendor/assets/javascripts/gulp/app.js`, as built by Gulp.
-
-```css
-//= require gulp/app
-```
-
-#### app/gulp/
-
-> Put your source files into `app/gulp`. For instance:
-
-* `app/gulp/example.css`
-
- ```css
-  * { color: blue }
-  ```
-
-* `app/gulp/example.js`
-
-  ```js
-  alert('it works!')
-  ```

data/docs/motivation.md

@@ -1,35 +0,0 @@
-# Motivation
-
-Rails's asset pipeline was a great step forward for Rails 3. For today's requirements however, it doesn't always come with all the tools you need. Here's a portrait of Rails's shortcomings with respect to CSS/JS development in 2016:
-
-* __npm assets:__ Frontend packages are now usually hosted in [npm], but there's no easy solution to integrate npm with Rails. Putting files into `vendor/assets` should be a thing of the past.
-
-* __Auto-reload:__ Automatic CSS reloading can be done with [guard-livereload], but is unwieldy at best. They require too much configuration and mental overhead to maintain.
-
-* __Modern CSS tools:__ Integrating modern CSS tools like [libsass] and [postcss] can be done, but is hackish and slow. It has to invoke a separate Node.js process for each CSS file rather than keeping those tools running in the background. Some newer CSS pre/post processors like [Myth](http://www.myth.io/) don't have production-grade integrations with Rails.
-
-* __Modern JS tools:__ Working with complex frontends typically need [Webpack] or [Browserify]. While integrations for these exist, they can be slow and unreliable.
-
-## Using Node.js
-
-npm-pipeline-rails lets you outsource asset building complexities to Node.js-based tools, which is the gold stardard for asset tooling nowadays.
-
-It doesn't lock you into one specific solution; you can use npm-pipeline-rails for any task manager. I recommend [Brunch] for its ease-of-use and familiarity with Rails's asset pipeline's features. [Gulp] and [Grunt] are also popular choices.
-
-## Brunch
-
-You can use [Brunch] with Rails with ease using npm-pipeline-rails. With Brunch, you get [automatic code reloading][auto-reload-brunch], easier integration with [postcss][postcss-brunch], `require()` support, and more. You may even hook [Browserify][browserify-brunch] if you need it.
-
-[guard-livereload]: http://rubygems.org/gems/guard-livereload
-[npm]: http://npmjs.com/
-[libsass]: http://sass-lang.com/libsass
-[postcss]: https://github.com/postcss/postcss
-[auto-reload-brunch]: https://www.npmjs.com/package/auto-reload-brunch
-[postcss-brunch]: https://www.npmjs.com/package/postcss-brunch
-[browserify-brunch]: https://www.npmjs.com/package/browserify-brunch
-[Grunt]: http://gruntjs.com/
-[Webpack]: https://webpack.github.io/
-[Brunch]: http://brunch.io/
-[Browserify]: http://browserify.org/
-[Gulp]: http://gulpjs.com/
-[Grunt]: http://gruntjs.com/