npm-pipeline-rails 1.6.1 → 1.6.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: b4cf04399ae70cea783c65554533be5c0bfa8567
-  data.tar.gz: ac7799a8a5379bc99868f0b90882f5508e00a77d
+  metadata.gz: f96251273b37786bd49553b430ac3edc6b80c3be
+  data.tar.gz: 6578229c4fddb49e68e0711285cefa67c17b4e88
 SHA512:
-  metadata.gz: b7c069c95bd71d98c1e3cd89be45d4084bfcce8f3362ad508c09031757613b62f3c8a68b308ba0f337dff36754c268b377851c0e3ba67733f463d3849db9f79e
-  data.tar.gz: e29a21e9d22c2886f7ac04ce7c21d1e8fc7444529ddf5949f84107e06d8a1b7089f5d245df52020dd900e0e0c32144bfde3511d92d1d975cadf8c9efcfc48e02
+  metadata.gz: d92db5d305c11a4bc3a9dd316564389038658a878310c991025cd8ce3856aebbbf96bf228288414d77924ca40d67400b99997eb33efdd5063c12e4c8de351e95
+  data.tar.gz: 8661f19a49117d1f3bf6f14b5e500bb4af3618624d3395ca02308d8c1808f5810d53e5717d9b90e1cafaedeeecbf6e2cda682274e0badaf241a56bedd382e062

data/HISTORY.md

@@ -1,3 +1,10 @@
+## [v1.6.2]
+> Oct 14, 2016
+
+- [#11] - Fix `rails generate npm_pipeline:gulp` not giving a working setup. ([@aka-cronos])
+
+[v1.6.2]: https://github.com/rstacruz/npm-pipeline-rails/compare/v1.6.1...v1.6.2
+
 ## [v1.6.1]
 > May 27, 2016
 
@@ -85,3 +92,5 @@
 [@jasontorres]: https://github.com/jasontorres
 [@victorsolis]: https://github.com/victorsolis
 [@mikker]: https://github.com/mikker
+[#11]: https://github.com/rstacruz/npm-pipeline-rails/issues/11
+[@aka-cronos]: https://github.com/aka-cronos

data/README.md

@@ -57,9 +57,13 @@ Use the generators for your preferred build tool:
 
 #### Set up support for tests
 
-If you're using continuous integration for your tests, configure it to run `bundle exec rake assets:npm_build` before your tests.
+If you're using continuous integration for your tests, configure it to run this before your tests:
 
-For tests running in your development machine, ensure that asset files are available when running your tests. This means starting your dev server at least once before running tests, or invoking `rake assets:npm_build` manually.
+```sh
+npm run build
+```
+
+For tests running in your development machine, ensure that asset files are available when running your tests. This means starting your dev server at least once before running tests, or invoking `npm run build` manually.
 
 #### Disable some gems
 
@@ -74,20 +78,24 @@ You may also want to disable some gems, depending on your set up:
 
 ## Heroku
 
-In Heroku, this requires the [Node.js](https://github.com/heroku/heroku-buildpack-nodejs) and [Ruby](https://github.com/heroku/heroku-buildpack-ruby) buildpacks. See: [Using Multiple Buildpacks for an App](https://devcenter.heroku.com/articles/using-multiple-buildpacks-for-an-app) *(devcenter.heroku.com)*
+When deploying to [Heroku](https://heroku.com), use [Node.js](https://github.com/heroku/heroku-buildpack-nodejs) and [Ruby](https://github.com/heroku/heroku-buildpack-ruby) buildpacks together. See: [Using Multiple Buildpacks for an App](https://devcenter.heroku.com/articles/using-multiple-buildpacks-for-an-app) *(devcenter.heroku.com)*
 
-```
-heroku buildpacks:set heroku/ruby
-heroku buildpacks:add --index 1 heroku/nodejs
+```sh
+$ heroku buildpacks:set heroku/ruby
+$ heroku buildpacks:add --index 1 heroku/nodejs
+
+Buildpack added. Next release on my-app-name will use:
+  1. heroku/nodejs
+  2. heroku/ruby
 ```
 
-Also see [Configuration](#configuration) on how to turn off `config.npm.install_on_asset_precompile`.
+It's recommended to turn off `config.npm.install_on_asset_precompile` to make deployments faster; see [§ Configuration](#configuration).
 
 <br>
 
 ## Configuration
 
-npm-pipeline-rails provides these configuration options:
+npm-pipeline-rails provides these configuration options below. Put them inside `config/application.rb` (not in an initializer!).
 
 ```rb
 # These are defaults; in most cases, you don't need to configure anything.
@@ -142,6 +150,20 @@ Consult [railtie.rb](https://github.com/rstacruz/npm-pipeline-rails/blob/master/
 
 <br>
 
+## Yarn
+
+To use [Yarn](https://yarnpkg.com/) instead of npm, change `config.npm.install` as seen below in `config/application.rb`. See [§ Configuration](#configuration) for more details.
+
+```rb
+Rails.application.configure do
+  # ...
+
+  config.npm.install = ['yarn']
+end
+```
+
+<br>
+
 ## Skipping Rails asset pipeline
 
 The recommended setup renders files to `vendor/assets/stylesheets/brunch/` and `vendor/assets/javascripts/brunch/`. (Replace `brunch` with whatever build tool you use.) You may opt to output to `public/assets/stylesheets/` and `public/assets/javascripts/` instead.

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

@@ -1,3 +1,3 @@
 module NpmPipelineRails
-  VERSION = '1.6.1'
+  VERSION = '1.6.2'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: npm-pipeline-rails
 version: !ruby/object:Gem::Version
-  version: 1.6.1
+  version: 1.6.2
 platform: ruby
 authors:
 - Rico Sta. Cruz
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2016-09-25 00:00:00.000000000 Z
+date: 2016-10-14 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: railties