webpacked 0.1.0 → 0.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 2ce3d51fcf3507e85c3cbf4d1fcc7c69c87cb4e7
-  data.tar.gz: bf49978a1f8e89013bb85c874ad1bfc33a098898
+  metadata.gz: a831df23a305a0f70f2a8dbf00b823267212491f
+  data.tar.gz: 0c2846787f6de4d1c101da0831a55612fe8e5a2f
 SHA512:
-  metadata.gz: 2c4a063a8c24b5dbe279bc6cc147eb527120a650dc1182bdc1625b0fcae431348f1988630ee93708d688bd9a054707ba0dd9df1e7db0f4ec0d42fb1d0249d579
-  data.tar.gz: 045b0f5f1f83a426f9546f926ee6902b366b9cef4f8d06968e4b87effebb91c86859620e12dc0514ed6468af912d33fcc490435d96140f6f04e4267292c88e38
+  metadata.gz: 32485b777d6fa441fbd41b4ccf2782ec36736632238ed0823563fea4b345d624765253539421ff8f64786f8fcd180aa1defd98c53e9fb7858c21f99217297fcc
+  data.tar.gz: 0c6e740686f93e77a0a54097334c80f1658c333a8c3b73062057c26a1fef61845c3c0c0879852348fe42753db1395974b85353e920cafc56580d605d72908725

data/README.md

@@ -33,7 +33,7 @@ Webpack configs are divided into on three files:
   1. `frontend/development.config.js` contains setup specific for development
   1. `frontend/production.config.js` includes production optimizations
 
-Follow comments in these files and webpack official docs to conclude what meets you requirements.
+Follow the comments in these files and webpack official docs to conclude what meets your requirements.
 
 Environment is defined via `NODE_ENV` variable and initialized in`frontend/main.config.js`. Normally you don't need to manual set up `NODE_ENV` unless you want to add another environment for your frontend application.
 
@@ -61,9 +61,9 @@ To add webpacked assets in to your application, use following helpers:
 </html>
 ```
 
-Where `'application'` is a one of the your entry points in webpack config.
+Where `application` is a one of the your entry points in webpack config.
 
-NOTE: if you using [common chunks optimization](https://webpack.github.io/docs/code-splitting.html#split-app-and-vendor-code) (it is so indeed in production most likely), these helpers may produce additional CSS/Javascript include tag for that common bundle.
+**NOTE**: if you using [common chunks optimization](https://webpack.github.io/docs/code-splitting.html#split-app-and-vendor-code) (it is so indeed in production most likely), these helpers may produce additional CSS/Javascript include tag for that common bundle.
 
 You should not concern about including any extra scripts to get hot module reloading works: it integrates transparently through a same webpack manifest file.
 
@@ -109,7 +109,7 @@ Gem exposes a few configuration options:
   * `webpacked.enabled` default to `true`; you probably want to disable webpacked in test environment, so helpers will not fail if manifest does not exist
   * `webpacked.manifest_path` default to `webpack-assets.json`
   * `webpacked.load_manifest_on_initialize` default to `false`; if `true` then parse manifest on application bootstrap
-  * `webpacked.common_entry_name` default to `common` (if you've changes this, you need to change it in webpack config as well)
+  * `webpacked.common_entry_name` default to `common` (if you've changed this, you need to update it in the webpack config as well)
   * `webpacked.bin` default to `node_modules/.bin/webpack`
   * `webpacked.config` default to `frontend/main.config.js`
   * `webpacked.dev_server` enabled only in development mode
@@ -120,13 +120,16 @@ Gem exposes a few configuration options:
 
 ### Installation and usage
 
-To deploy generated assets add `require "capistrano/webpacked"` to your `Capfile`. The `deploy:webpacked:build` task will run automaticaly as after `deploy:updated` hook.
+To deploy generated assets add `require "capistrano/webpacked"` to your `Capfile`.
 
-Also you need to set up the `:assets_roles` in `deploy.rb` so **webpacked** to run its tasks.
+Also you need to add some code in to `deploy.rb`:
 
-What under hood? The task makes diff of files and folders (specified in `:webpacked_dependencies` option) in current release against previous release and decides whether to run production webpack build. If there is no diff then simply a manifest copied from previous release path. If some of dependencies were changed then production build starts *locally* and assets synchronized via `rsync` over SSH.
+  * set up the `:assets_roles` so **webpacked** could run its tasks
+  * define a hook when the task should be run: `after 'deploy:updated', 'deploy:webpacked:build'` or (if you use sprockets) `before 'deploy:compile_assets', 'deploy:webpacked:build'` are good variants
 
-NOTE: scince webpack build runs locally, you should pay an extra attention to your working copy condition: current branch, not published commits, not commited changes, etc.
+What under the hood? The task makes diff of files and folders (specified in `:webpacked_dependencies` option) in current release against previous release and decides whether to run production webpack build. If there is no diff then simply a manifest copied from previous release path. If some of dependencies were changed then production build starts *locally* and assets synchronized via `rsync` over SSH.
+
+**NOTE**: scince webpack build runs locally, you should pay an extra attention to your working copy condition: current branch, not published commits, not commited changes, etc.
 
 Additionally there are some extra tasks exposed (they are used by `deploy:webpacked:build` internally):
 

data/lib/capistrano/tasks/webpacked.rake

@@ -36,6 +36,12 @@ namespace :deploy do
               end
             end
 
+            latest_manifest_path = latest_release_path.join(OPTIONS.(:manifest_path))
+            unless test("[[ -f #{latest_manifest_path} ]]")
+              info "Latest webpack manifest not found: #{latest_manifest_path}. Need rebuild"
+              raise WebpackedBuildRequired
+            end
+
             info 'Skipping webpack build, no diff found'
 
             execute(
@@ -49,7 +55,6 @@ namespace :deploy do
         end
       end
     end
-    after 'deploy:updated', 'deploy:webpacked:build'
 
     task :build_force do
       run_locally do
@@ -63,7 +68,6 @@ namespace :deploy do
 
     task :sync do
       on roles(fetch(:assets_roles)) do
-        info 'Sync assets...'
         upload!(
           OPTIONS.(:deploy_manifest_path),
           release_path.join(OPTIONS.(:manifest_path))
@@ -72,7 +76,8 @@ namespace :deploy do
       end
       roles(fetch(:assets_roles)).each do |host|
         run_locally do
-          local_output_path = fetch(:webpacked_local_output_path)
+          info 'Sync assets...'
+          local_output_path = OPTIONS.(:local_output_path)
           release_output_path = shared_path.join(OPTIONS.(:release_output_path))
           `rsync -avzr --delete #{local_output_path} #{host.user}@#{host.hostname}:#{release_output_path.parent}`
         end

data/lib/webpacked/version.rb

@@ -1,3 +1,3 @@
 module Webpacked
-  VERSION = '0.1.0'
+  VERSION = '0.1.2'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: webpacked
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.1.2
 platform: ruby
 authors:
 - Andrey Garbuz
@@ -87,7 +87,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.6.6
+rubygems_version: 2.6.4
 signing_key: 
 specification_version: 4
 summary: Easy webpack and Rails integration