browserify-rails 0.8.0 → 0.8.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +4 -0
- data/README.md +4 -0
- data/lib/browserify-rails/railtie.rb +3 -1
- data/lib/browserify-rails/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: c4e833f60ddfd44e1c1c4af7e7f6238667d630e4
|
4
|
+
data.tar.gz: 22cf219d2d13b81a6aa37232835dba90da424171
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: bda27a59ae871de6fdeeb6d7a1e6e48f102712647d3103236a2335345dc1b0b489ddcc4013a784ed4a37cef337e1fb2339c4865a3c39eca289967f835498eb38
|
7
|
+
data.tar.gz: a00f43d0187a1124cee3b3ce057e68c5720fc8e29d29b158e51b0a5752de1a75aff097ec1010822ba05da3c5a097b04d468445488380707191b278177c5419f8
|
data/CHANGELOG.md
CHANGED
@@ -1,6 +1,10 @@
|
|
1
1
|
# Change Log
|
2
2
|
All notable changes to this project will be documented in this file going forward.
|
3
3
|
|
4
|
+
## [0.8.1] - 2015-03-17
|
5
|
+
### Changed
|
6
|
+
- disable browserify-incremental in production and staging environments
|
7
|
+
|
4
8
|
## [0.8.0] - 2015-03-17
|
5
9
|
### Changed
|
6
10
|
- do not compile source maps for any environment by default (used to default to development-enabled)
|
data/README.md
CHANGED
@@ -121,6 +121,10 @@ class My::Application < Rails::Application
|
|
121
121
|
config.browserify_rails.commandline_options = "-t browserify-shim --fast"
|
122
122
|
```
|
123
123
|
|
124
|
+
### browserify-incremental
|
125
|
+
|
126
|
+
[browserify-incremental](https://github.com/jsdf/browserify-incremental) is used to cache browserification of CommonJS modules. One of the side effects is that the absolute module path is included in the emitted JavaScript. Most people do not want this for production code so browerify-incremental is current disabled for the `production` and `staging` environments. Note that counter-intuitively, browserify-incremental helps even with a single build pass of your code because typically the same modules are used multiple times. So it helps even for say asset compilation on a push to Heroku.
|
127
|
+
|
124
128
|
### Multiple bundles
|
125
129
|
|
126
130
|
node-browserify supports [multiple bundles](https://github.com/substack/node-browserify#multiple-bundles)
|
@@ -18,7 +18,9 @@ module BrowserifyRails
|
|
18
18
|
config.browserify_rails.source_map_environments = []
|
19
19
|
|
20
20
|
# Use browserifyinc instead of browserify
|
21
|
-
|
21
|
+
# TODO figure out how to handle module paths being in output
|
22
|
+
# until then, disable in staging and production
|
23
|
+
config.browserify_rails.use_browserifyinc = !["staging", "production"].include?(Rails.env)
|
22
24
|
|
23
25
|
initializer :setup_browserify do |app|
|
24
26
|
# Load granular configuration
|