jsbundling-rails 1.1.1 → 1.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 137e2a80465a741d5a59b07f3776f8de07461e782439f64f7a096ac9f46f4446
-  data.tar.gz: 47ddd6de7ec38dbaaf5568c433723cf79c3f93a0b4409b580c85b7fceb5dbb01
+  metadata.gz: e87af17983ef465c2f92f63a3943df1ed2f1508eec23644f4134bdef5430ec27
+  data.tar.gz: de600a6cefeb7f190d1348f7edbe328d71fe13aeff2dd8903dcc4ff78a029a60
 SHA512:
-  metadata.gz: 04222ea64e7bf09c63fef4dddabc1e9537960fecf6629dcca6c3417c31bbfc580d0de716c45b8c9638e60d8c80cee213aa2263b4c0ed2cebf47d49f47f48079f
-  data.tar.gz: ef8f1a586d142d28d4399530a1cdc34065f59ebf23e0446d0fda349ceaefd82dc4377382b9e7ad53c412e89ec03e73562809ba81d05f5a9db47bcfee47776f97
+  metadata.gz: 06f0040b3476411f6bcb1bfcef1280763161c53a2dddb9087c180f31e8b360992dcb6191aa04c08755298d69b3f5671a5583a435b1a988b55fca2370a794958f
+  data.tar.gz: 18f37485ec256760ed0343d820da6798b6e2f358d4db3c9a653f4d95ccc961c11db4380c25add8d2e6776bcbc058e56229563c7d4fb261b53efc9f9f795335fb

data/README.md

@@ -8,9 +8,7 @@ Whenever the bundler detects changes to any of the JavaScript files in your proj
 
 When you deploy your application to production, the `javascript:build` task attaches to the `assets:precompile` task to ensure that all your package dependencies from `package.json` have been installed via yarn, and then runs `yarn build` to process all the entry points, as it would in development. The latter files are 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 the bundler attaches to the `test:prepare` task to ensure the JavaScript has been bundled 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`).
-
-If your testing library of choice does not define a `test:prepare` Rake task, ensure that your test suite runs `javascript:build` to bundle JavaScript before testing commences.
+This also happens in testing where the bundler attaches to the `test:prepare` task to ensure the JavaScript has been bundled before testing commences. If your testing library of choice does not call the `test:prepare` Rake task, ensure that your test suite runs `javascript:build` to bundle JavaScript before testing commences.
 
 That's it!
 
@@ -22,10 +20,15 @@ If you want to use webpack features like [code splitting](https://webpack.js.org
 
 ## Installation
 
-You must already have node and yarn installed on your system. You will also need npx version 7.1.0 or later. Then:
+You must already have node and yarn installed on your system. You will also need npx version 7.1.0 or later. Then run:
+
+```
+./bin/bundle add jsbundling-rails
+```
 
-1. Run `./bin/bundle add jsbundling-rails`
-2. Run `./bin/rails javascript:install:[esbuild|rollup|webpack]`
+```
+./bin/rails javascript:install:[esbuild|rollup|webpack]
+```
 
 Or, in Rails 7+, you can preconfigure your new application to use a specific bundler with `rails new myapp -j [esbuild|rollup|webpack]`.
 
@@ -45,11 +48,13 @@ If you [import CSS](https://esbuild.github.io/content-types/#css-from-js) in you
 Suppose you have an image `app/javascript/images/example.png` that you need to reference in frontend code built with esbuild.
 
 1. Create the image at `app/javascript/images/example.png`.
-1. In `package.json`, under `"scripts"` and `"build"`, add the option `--loader:.png=file` to the esbuild script, which instructs esbuild to copy png files to the build directory.
-1. When esbuild runs, it will copy the png file to something like `app/assets/builds/example-5SRKKTLZ.png`.
+1. In `package.json`, under `"scripts"` and `"build"`, add the additional arguments:
+    * `--loader:.png=file` This instructs esbuild to copy png files to the build directory.
+    * `--asset-names=[name]-[hash].digested` This tells esbuild to append `.digested` to the file name so that sprockets or propshaft will not append an additional digest hash to the file.
+1. When esbuild runs, it will copy the png file to something like `app/assets/builds/example-5SRKKTLZ.digested.png`.
 1. In frontend code, the image is available for import by its original name: `import Example from "../images/example.png"`.
 1. The image itself can now be referenced by its imported name, e.g. in React, `<img src={Example} />`.
-1. The path of the image resolves to `/assets/example-5SRKKTLZ.png`, which is served by the asset pipeline.
+1. The path of the image resolves to `/assets/example-5SRKKTLZ.digested.png`, which is served by the asset pipeline.
 
 ## License
 

data/lib/install/Procfile.dev

@@ -1,2 +1,2 @@
-web: unset PORT && bin/rails server
+web: unset PORT && env RUBY_DEBUG_OPEN=true bin/rails server
 js: yarn build --watch

data/lib/install/esbuild/install.rb

@@ -2,7 +2,7 @@ say "Install esbuild"
 run "yarn add esbuild"
 
 say "Add build script"
-build_script = "esbuild app/javascript/*.* --bundle --sourcemap --outdir=app/assets/builds --public-path=assets"
+build_script = "esbuild app/javascript/*.* --bundle --sourcemap --outdir=app/assets/builds --public-path=/assets"
 
 case `npx -v`.to_f
 when 7.1...8.0

data/lib/install/rollup/rollup.config.js

@@ -4,7 +4,7 @@ export default {
   input: "app/javascript/application.js",
   output: {
     file: "app/assets/builds/application.js",
-    format: "es",
+    format: "iife",
     inlineDynamicImports: true,
     sourcemap: true
   },

data/lib/jsbundling/version.rb

@@ -1,3 +1,3 @@
 module Jsbundling
-  VERSION = "1.1.1"
+  VERSION = "1.1.2"
 end

data/lib/tasks/jsbundling/build.rake

@@ -1,10 +1,18 @@
 namespace :javascript do
+  desc "Install JavaScript dependencies"
+  task :install do
+    unless system "yarn install"
+      raise "jsbundling-rails: Command install failed, ensure yarn is installed"
+    end
+  end
+
   desc "Build your JavaScript bundle"
-  task :build do
-    unless system "yarn install && yarn build"
-      raise "jsbundling-rails: Command build failed, ensure yarn is installed and `yarn build` runs without errors"
+  build_task = task :build do
+    unless system "yarn build"
+      raise "jsbundling-rails: Command build failed, ensure `yarn build` runs without errors"
     end
   end
+  build_task.prereqs << :install unless ENV["SKIP_YARN_INSTALL"]
 end
 
 if Rake::Task.task_defined?("assets:precompile")

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: jsbundling-rails
 version: !ruby/object:Gem::Version
-  version: 1.1.1
+  version: 1.1.2
 platform: ruby
 authors:
 - David Heinemeier Hansson
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2022-12-14 00:00:00.000000000 Z
+date: 2023-06-18 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: railties
@@ -67,7 +67,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.3.26
+rubygems_version: 3.4.10
 signing_key:
 specification_version: 4
 summary: Bundle and transpile JavaScript in Rails with esbuild, rollup.js, or Webpack.