jsbundling-rails 0.2.1 → 0.2.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2c0462a5cd60b4d9f11d5f1b422675b6e2057a05389833bd81246d3242847dfe
-  data.tar.gz: 847fd31b04ad34182e10dcf4e5157055dafae83bcf13c435cd6ee4cea7fcf440
+  metadata.gz: da26b732da73b487d5947d452d49b253b7dc19b134a213c14295085f38ac960f
+  data.tar.gz: 5070afe7f7681941291659451972f8dcaad1a5bb25e34edac521b8a540e54012
 SHA512:
-  metadata.gz: 954a585f3da1bd9e957698438462b977539cf6ba59fa2957f9d4fd4e277d6284ce197138af964eef32bff893b4567b227fb6812b28b2a48eb2bee48702303828
-  data.tar.gz: 924e4d2a47c5bbed32f848264ecb8cb67e39e899c8d25e647ca110dec7dfa142c3a7228678da4492f8fceb511f6a4c3ce638d18181783f2efa1b0125bd8a5a27
+  metadata.gz: bbc6ce778dc63da90bec9217ba2f869bcf04453160f63106f357a1cc967f1dede7828cdc04f852ae1187d4208faf95b7ab4295043afeafe2b70e6a187cf03ee2
+  data.tar.gz: 5d7b9e5b4cd21f408c9b657bcaa62401769e249c617980781a33b6445178e34777db17b6db5079589064697faaa8dd4b3f05e3384c3f5bb5e63f86caf19b0636

data/README.md

@@ -38,7 +38,7 @@ The default build script for esbuild relies on the `app/javascript/*.*` glob pat
 
 ## Why does esbuild overwrite my application.css?
 
-If you [import CSS](https://esbuild.github.io/content-types/#css-from-js) in your application.js while using esbuild, you'll be creating both an `app/assets/builds/application.js` _and_ `app/assets/builds/application.css` file when bundling. The latter can conflict with the `app/assets/builds/application.js` produced by [cssbundling-rails](https://github.com/rails/cssbundling-rails). The solution is to either change the output file for esbuild (and the references for that) or for cssbundling. Both are specified in `package.json`. 
+If you [import CSS](https://esbuild.github.io/content-types/#css-from-js) in your application.js while using esbuild, you'll be creating both an `app/assets/builds/application.js` _and_ `app/assets/builds/application.css` file when bundling. The latter can conflict with the `app/assets/builds/application.css` produced by [cssbundling-rails](https://github.com/rails/cssbundling-rails). The solution is to either change the output file for esbuild (and the references for that) or for cssbundling. Both are specified in `package.json`. 
 
 
 ## License

data/lib/install/esbuild/install.rb

@@ -8,4 +8,5 @@ if (`npx -v`.to_f < 7.1 rescue "Missing")
   say %(Add "scripts": { "build": "#{build_script}" } to your package.json), :green
 else
   run %(npm set-script build "#{build_script}")
+  run %(yarn build)
 end

data/lib/install/rollup/install.rb

@@ -9,4 +9,5 @@ if (`npx -v`.to_f < 7.1 rescue "Missing")
   say %(Add "scripts": { "build": "#{build_script}" } to your package.json), :green
 else
   run %(npm set-script build "#{build_script}")
+  run %(yarn build)
 end

data/lib/install/webpack/install.rb

@@ -9,4 +9,5 @@ if (`npx -v`.to_f < 7.1 rescue "Missing")
   say %(Add "scripts": { "build": "#{build_script}" } to your package.json), :green
 else
   run %(npm set-script build "#{build_script}")
+  run %(yarn build)
 end

data/lib/jsbundling/version.rb

@@ -1,3 +1,3 @@
 module Jsbundling
-  VERSION = "0.2.1"
+  VERSION = "0.2.2"
 end

data/lib/tasks/jsbundling/clobber.rake

@@ -4,3 +4,5 @@ namespace :javascript do
     rm_rf Dir["app/assets/builds/[^.]*.js"], verbose: false
   end
 end
+
+Rake::Task["assets:clobber"].enhance(["javascript:clobber"])

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: jsbundling-rails
 version: !ruby/object:Gem::Version
-  version: 0.2.1
+  version: 0.2.2
 platform: ruby
 authors:
 - David Heinemeier Hansson
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2021-11-17 00:00:00.000000000 Z
+date: 2021-12-03 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: railties