rollupjs-rails 0.1.0 → 0.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: b6e88daac911ff6400da2b84ebc8be3cded0c243b3644a1ad3a4354aa19a143a
-  data.tar.gz: 67c7ffb6091d8ebc3b0314ef45dcffc72d8060ea10fcb76ffa823f8f32b3546e
+  metadata.gz: e76dd98fb4680e49d6d0b119aac29ffe507e3bb37af760416d7fc247df5871db
+  data.tar.gz: 3ebd46a7a6598c1beb8a8b99ced16971a2ab5dc02b61c72dc7791befa2d5bc10
 SHA512:
-  metadata.gz: 7a675b399fd14abcca4a4df3cd83ffeaf32180bcdaa69c503760374dfa73e9953be03abeaeada11ed877d0ec7787e77a1bef4999996e18326f234d2a98275219
-  data.tar.gz: f5d4920d160822ba89236413616931a7c096258eaf9478096171126986df9cd3e4ae9c439fc979c5f42bb48c6614b1b9be0913915d50a224045c325abd036dc8
+  metadata.gz: b6bf58532dee189761fcaf6e3db3f6e077279ec21742c4aeac040a776bfd3c00b2a006a14292f20b8b8de6b024925a8ac75d6f215158ede9b1232a615c82a906
+  data.tar.gz: 99908c39a0a347b44f26931af1a37556d5612848a673c25279dc060dd1090048a35c9e201a76bcb94133282afaf999d6fa2301117688aeb874f5fcef589aeb3c

data/README.md

@@ -6,6 +6,8 @@ You develop using this approach by running rollup.js in watch mode in a terminal
 
 When you deploy your application to production, rollup.js attaches to the `assets:precompile` task to ensure that all your package dependencies from `package.json` have been installed via npm, and then runs `yarn build` to process `app/javascript/application.js` into `app/assets/builds/javascript.js`. The latter file is then picked up by the asset pipeline, digested, and copied into public/assets, as any other asset pipeline file.
 
+This also happens in testing where rollup attaches to the `test:prepare` task to ensure the JavaScript has been compiled before testing commences. (Note that this currently only applies to rails `test:*` tasks (like `test:all` or `test:controllers`), not "rails test", as that doesn't load `test:prepare`).
+
 That's it!
 
 You can tailor the configuration of rollup.js through the `rollup.config.js` that's created in the root of your project by the installer.
@@ -24,7 +26,7 @@ Or, in Rails 7+, you can preconfigure your new application to use rollup.js with
 
 ## The sister gem to esbuild-rails
 
-This gem is almost identical in setup and purpose as [`esbuild-rails`](https://github.com/rails/esbuild-rails), which follows the same conventions, but uses [esbuild](https://esbuild.github.io) instead.
+This gem is almost identical in setup and purpose to [`esbuild-rails`](https://github.com/rails/esbuild-rails), which follows the same conventions, but uses [esbuild](https://esbuild.github.io) instead.
 
 
 ## License

data/lib/rollup/version.rb

@@ -1,3 +1,3 @@
 module Rollup
-  VERSION = "0.1.0"
+  VERSION = "0.1.1"
 end

data/lib/tasks/rollup/compile.rake

@@ -6,3 +6,4 @@ namespace :rollup do
 end
 
 Rake::Task["assets:precompile"].enhance(["rollup:compile"])
+Rake::Task["test:prepare"].enhance(["rollup:compile"])

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: rollupjs-rails
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.1.1
 platform: ruby
 authors:
 - David Heinemeier Hansson
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2021-09-04 00:00:00.000000000 Z
+date: 2021-09-05 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails