npm-pipeline-rails 1.1.0 → 1.1.1

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: cf569c96c85c02b65915d854b5ed6023012bc7aa
4
- data.tar.gz: d0e38db04bb99ed44153f96d65740caddda891a2
3
+ metadata.gz: 87487679b6a5d6d28e33ac1e5a5159c196d4a7bb
4
+ data.tar.gz: 217798c9d06c247379afa503fd9564a9841c8539
5
5
  SHA512:
6
- metadata.gz: 1ef48bbe254b7960785f489b19401423419baa51776ebbe69837810c9bc78094fcd95107fc28376ca7a3b00f82a9b48b96d000c550fce141f5b57fa7ca5378ed
7
- data.tar.gz: b8f655d71c5eab1cd5b1ecc7bd1fc8832a44e035fae1435b2e16fd9e7ee36d0315fcf2a1d2183f7ab7902ac239bab37809b348777a10b03946e423f7ce9bfbf6
6
+ metadata.gz: d08900a5c70f9f8d3ef96a26adcba6708ffb631669fc0b730a7b64578dd87dcfda16fc01955f5f2ca3bc7344ec2cc3d91f4eb093f04a963c6ebdf2314469673c
7
+ data.tar.gz: 256921cb8f32fd7081fc6396f9d17fcd61b88942e57b1f3eee317ed3e8fa3e9aa04f8837ae61ffd85fc48601d62cbce424f7fac6134378fcf09e54ba9e497c44
data/HISTORY.md CHANGED
@@ -1,3 +1,10 @@
1
+ ## [v1.1.1]
2
+ > Mar 22, 2016
3
+
4
+ - Update documentation and gem description; no functional changes.
5
+
6
+ [v1.1.1]: https://github.com/rstacruz/npm-pipeline-rails/compare/v1.1.0...v1.1.1
7
+
1
8
  ## [v1.1.0]
2
9
  > Mar 22, 2016
3
10
 
data/README.md CHANGED
@@ -36,13 +36,22 @@ gem 'npm-pipeline-rails'
36
36
 
37
37
  #### Automated setup
38
38
 
39
- * Run `./bin/rails generate npm_pipeline:brunch` to add a sample integration with [Brunch]. ([info](docs/brunch.md))
39
+ Use the generators for your preferred build tool:
40
+
41
+ - __[Brunch](docs/brunch.md)__ - `./bin/rails generate npm_pipeline:brunch`
42
+ - __[Gulp](docs/gulp.md)__ - `./bin/rails generate npm_pipeline:gulp`
40
43
 
41
44
  #### Manual setup
42
45
 
43
46
  * Create a `package.json` with `start` and `build` scripts. ([See example](lib/generators/npm_pipeline/brunch/package.json))
44
47
  * Add your expected compiled assets to `.gitignore`.
45
48
 
49
+ #### Set up support for tests
50
+
51
+ If you're using continuous integration for your tests, configure it to run `bundle exec rake assets:npm_build` before your tests.
52
+
53
+ 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.
54
+
46
55
  <br>
47
56
 
48
57
  ## Configuration
@@ -92,12 +101,6 @@ Consult [railtie.rb](https://github.com/rstacruz/npm-pipeline-rails/blob/master/
92
101
 
93
102
  <br>
94
103
 
95
- ## Integration examples
96
-
97
- * [Brunch](docs/brunch.md)
98
-
99
- <br>
100
-
101
104
  ## Motivation
102
105
 
103
106
  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. npm-pipeline-rails lets you outsource asset building complexities to Node.js-based tools.
data/docs/brunch.md CHANGED
@@ -1,24 +1,30 @@
1
1
  # Brunch integration
2
2
 
3
- Run `./bin/rails generate npm_pipeline:brunch`.
3
+ Run this to set your project up with a simple Brunch config.
4
+
5
+ ```sh
6
+ ./bin/rails generate npm_pipeline:brunch
7
+ ```
4
8
 
5
9
  ## Manual setup
6
10
 
7
11
  If you don't want to use the generator, here's what it does.
8
12
 
9
- ### brunch-config.js
13
+ #### package.json
14
+
15
+ > Set it up with `brunch` and some basic plugins.
16
+
17
+ _See:_ [sample package.json](../lib/generators/npm_pipeline/brunch/package.json)
10
18
 
11
- Set it up to watch source files in `app/brunch`, then put built files into `vendor/assets`.
12
- [See example.](../lib/generators/npm_pipeline/brunch/brunch-config.js)
19
+ #### brunch-config.js
13
20
 
14
- ### package.json
21
+ > Set it up to watch source files in `app/brunch`, then put built files into `vendor/assets`.
15
22
 
16
- Set it up with `brunch` and some basic plugins.
17
- [See example.](../lib/generators/npm_pipeline/brunch/package.json)
23
+ _See:_ [sample brunch-config.js](../lib/generators/npm_pipeline/brunch/brunch-config.js)
18
24
 
19
- ### .gitignore
25
+ #### .gitignore
20
26
 
21
- Set it up to ignore Brunch's built files.
27
+ > Set it up to ignore Brunch's built files.
22
28
 
23
29
  ```
24
30
  /node_modules
@@ -26,9 +32,9 @@ Set it up to ignore Brunch's built files.
26
32
  /vendor/assets/javascripts/brunch
27
33
  ```
28
34
 
29
- ### app/assets/stylesheets/application.css
35
+ #### app/assets/stylesheets/application.css
30
36
 
31
- Set it up to include Brunch's built files. This will load from `vendor/assets/stylesheets`, as built by Brunch.
37
+ > Set it up to include Brunch's built files. This will load from `vendor/assets/stylesheets/brunch/app.css`, as built by Brunch.
32
38
 
33
39
  ```css
34
40
  /*
@@ -36,17 +42,17 @@ Set it up to include Brunch's built files. This will load from `vendor/assets/st
36
42
  */
37
43
  ```
38
44
 
39
- ### app/assets/javascripts/application.js
45
+ #### app/assets/javascripts/application.js
40
46
 
41
- Set it up to include Brunch's built files. This will load from `vendor/assets/javascripts`, as built by Brunch.
47
+ > Set it up to include Brunch's built files. This will load from `vendor/assets/javascripts/brunch/app.js`, as built by Brunch.
42
48
 
43
49
  ```css
44
50
  //= require brunch/app
45
51
  ```
46
52
 
47
- ### app/brunch/
53
+ #### app/brunch/
48
54
 
49
- Put your source files into `app/brunch`. For instance:
55
+ > Put your source files into `app/brunch`. For instance:
50
56
 
51
57
  * `app/brunch/example.css`
52
58
 
data/docs/gulp.md CHANGED
@@ -1,23 +1,30 @@
1
1
  # Gulp integration
2
2
 
3
- Run `./bin/rails generate npm_pipeline:gulp`.
3
+ Run this to set your project up with a simple Gulp config.
4
+
5
+ ```sh
6
+ ./bin/rails generate npm_pipeline:gulp
7
+ ```
4
8
 
5
9
  ## Manual setup
6
10
 
7
11
  If you don't want to use the generator, here's what it does.
8
12
 
9
- ### package.json
13
+ #### package.json
14
+
15
+ > Set up `gulp`, `gulp-cli`, and some basic Gulp plugins.
16
+
17
+ _See:_ [sample package.json](../lib/generators/npm_pipeline/gulp/package.json)
10
18
 
11
- Set up `gulp`, `gulp-cli`, and some basic Gulp plugins.
12
- [See example.](../lib/generators/npm_pipeline/gulp/package.json)
19
+ #### gulpfile.js
13
20
 
14
- ### gulpfile.js
21
+ > Set it up to watch source files in `app/gulp`, then put built files into `vendor/assets`.
15
22
 
16
- Set it up to watch source files in `app/gulp`, then put built files into `vendor/assets`. [See example.](../lib/generators/npm_pipeline/gulp/gulpfile.js)
23
+ _See:_ [sample gulpfile.js](../lib/generators/npm_pipeline/gulp/gulpfile.js)
17
24
 
18
- ### .gitignore
25
+ #### .gitignore
19
26
 
20
- Set it up to ignore Gulp's built files.
27
+ > Set it up to ignore Gulp's built files.
21
28
 
22
29
  ```
23
30
  /node_modules
@@ -25,9 +32,9 @@ Set it up to ignore Gulp's built files.
25
32
  /vendor/assets/javascripts/gulp
26
33
  ```
27
34
 
28
- ### app/assets/stylesheets/application.css
35
+ #### app/assets/stylesheets/application.css
29
36
 
30
- Set it up to include Gulp's built files. This will load from `vendor/assets/stylesheets/gulp/app.css`, as built by Gulp.
37
+ > Set it up to include Gulp's built files. This will load from `vendor/assets/stylesheets/gulp/app.css`, as built by Gulp.
31
38
 
32
39
  ```css
33
40
  /*
@@ -35,25 +42,25 @@ Set it up to include Gulp's built files. This will load from `vendor/assets/styl
35
42
  */
36
43
  ```
37
44
 
38
- ### app/assets/javascripts/application.js
45
+ #### app/assets/javascripts/application.js
39
46
 
40
- Set it up to include Gulp's built files. This will load from `vendor/assets/javascripts/gulp/app.js`, as built by Gulp.
47
+ > Set it up to include Gulp's built files. This will load from `vendor/assets/javascripts/gulp/app.js`, as built by Gulp.
41
48
 
42
49
  ```css
43
50
  //= require gulp/app
44
51
  ```
45
52
 
46
- ### app/gulp/
53
+ #### app/gulp/
47
54
 
48
- Put your source files into `app/gulp`. For instance:
55
+ > Put your source files into `app/gulp`. For instance:
49
56
 
50
- * `app/brunch/example.css`
57
+ * `app/gulp/example.css`
51
58
 
52
59
  ```css
53
60
  * { color: blue }
54
61
  ```
55
62
 
56
- * `app/brunch/example.js`
63
+ * `app/gulp/example.js`
57
64
 
58
65
  ```js
59
66
  alert('it works!')
@@ -1,3 +1,3 @@
1
1
  module NpmPipelineRails
2
- VERSION = '1.1.0'
2
+ VERSION = '1.1.1'
3
3
  end
@@ -9,8 +9,8 @@ Gem::Specification.new do |spec|
9
9
  spec.authors = ['Rico Sta. Cruz']
10
10
  spec.email = ['rstacruz@users.noreply.github.com']
11
11
 
12
- spec.summary = 'Build your Rails assets with npm'
13
- spec.description = '...'
12
+ spec.summary = 'Use npm as part of your Rails asset pipeline'
13
+ spec.description = 'Use any toolchain to bulid your asset files in Rails 4.2. Integrate Brunch, Gulp, Grunt, Webpack, Browserify and others seamlessly into Rails apps.'
14
14
  spec.homepage = 'https://github.com/rstacruz/npm-pipeline-rails'
15
15
  spec.license = 'MIT'
16
16
 
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: npm-pipeline-rails
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.1.0
4
+ version: 1.1.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Rico Sta. Cruz
@@ -94,7 +94,8 @@ dependencies:
94
94
  - - "~>"
95
95
  - !ruby/object:Gem::Version
96
96
  version: '4.2'
97
- description: "..."
97
+ description: Use any toolchain to bulid your asset files in Rails 4.2. Integrate Brunch,
98
+ Gulp, Grunt, Webpack, Browserify and others seamlessly into Rails apps.
98
99
  email:
99
100
  - rstacruz@users.noreply.github.com
100
101
  executables: []
@@ -144,5 +145,5 @@ rubyforge_project:
144
145
  rubygems_version: 2.5.1
145
146
  signing_key:
146
147
  specification_version: 4
147
- summary: Build your Rails assets with npm
148
+ summary: Use npm as part of your Rails asset pipeline
148
149
  test_files: []