tailwindcss-rails 2.4.0-x64-mingw-ucrt → 2.5.0-x64-mingw-ucrt

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ff7099551b16f337b47edcb643a66ba0a0051f8e658c69a30c56214f8d0f9bc0
-  data.tar.gz: 5b5e8c030c347f5f737b009c57e53d4e2d76f95dddb1e8fe6cb301e753fa1460
+  metadata.gz: 45b9d872b3b676a9ea4bf9375d1faba3176b586f73f29e0ef7a3ae993b57b096
+  data.tar.gz: 8db69f7fa4bede9fd0548914f92c99d7a83251cc71568557336042b4f451614c
 SHA512:
-  metadata.gz: dbc2c5a6c0928061925d8cce17f68fe08f736bcfaf49766308b91e11e77a528b6fc1009c8d7cd649989ddd84f6312a72ebc4c28ba698e11219c6ca6824bbfbe7
-  data.tar.gz: c97e4c57cbb1ea6f47d81b6bd4a4f9495c7b4f992827e34eb1605e57c6b8c575016e7cc131cf89daae712ace839c0caab04c776f05bd3ffbc429184c9a69de30
+  metadata.gz: fefe77d1f0cc469f009367e3e5eb14de9b3bc03661ef98336977931c0e6b333f9719e90522700d167b8032786b818d08d632c1d49fa3b42a1bc7f8b79d9567a3
+  data.tar.gz: 3b551d9cdc31224544acdb3810edd101fe77533b82724654f59526654f808020b94add33dd0c3f41d8b1c46eb68389defc1a4b4ba7a8edfe3b6fee82a7997d47

data/README.md

@@ -17,6 +17,7 @@
   * [Using with PostCSS](#using-with-postcss)
   * [Custom inputs or outputs](#custom-inputs-or-outputs)
 - [Troubleshooting](#troubleshooting)
+  * [Lost keystrokes or hanging when using `ruby/debug` with the Puma plugin](#lost-keystrokes-or-hanging-when-using-rubydebug-with-the-puma-plugin)
   * [Running in a docker container exits prematurely](#running-in-a-docker-container-exits-prematurely)
   * [Conflict with sassc-rails](#conflict-with-sassc-rails)
   * [Class names must be spelled out](#class-names-must-be-spelled-out)
@@ -185,6 +186,10 @@ If you need to use a custom input or output file, you can run `bundle exec tailw
 
 Some common problems experienced by users ...
 
+### Lost keystrokes or hanging when using terminal-based debugging tools (e.g. IRB, Pry, `ruby/debug`...etc.) with the Puma plugin
+
+We've addressed the issue and you can avoid the problem by upgrading `tailwindcss-rails` to [v2.4.1](https://github.com/rails/tailwindcss-rails/releases/tag/v2.4.1) or later versions.
+
 ### Running in a docker container exits prematurely
 
 If you are running `rails tailwindcss:watch` as a process in a Docker container, set `tty: true` in `docker-compose.yml` for the appropriate container to keep the watch process running.

data/lib/install/tailwind.config.js

@@ -16,7 +16,6 @@ module.exports = {
   },
   plugins: [
     require('@tailwindcss/forms'),
-    require('@tailwindcss/aspect-ratio'),
     require('@tailwindcss/typography'),
     require('@tailwindcss/container-queries'),
   ]

data/lib/puma/plugin/tailwindcss.rb

@@ -8,7 +8,12 @@ Puma::Plugin.create do
     @puma_pid = $$
     @tailwind_pid = fork do
       Thread.new { monitor_puma }
-      system(*Tailwindcss::Commands.watch_command)
+      # Using IO.popen(command, 'r+') will avoid watch_command read from $stdin.
+      # If we use system(*command) instead, IRB and Debug can't read from $stdin
+      # correctly bacause some keystrokes will be taken by watch_command.
+      IO.popen(Tailwindcss::Commands.watch_command, 'r+') do |io|
+        IO.copy_stream(io, $stdout)
+      end
     end
 
     launcher.events.on_stopped { stop_tailwind }

data/lib/tailwindcss/version.rb

@@ -1,3 +1,3 @@
 module Tailwindcss
-  VERSION = "2.4.0"
+  VERSION = "2.5.0"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: tailwindcss-rails
 version: !ruby/object:Gem::Version
-  version: 2.4.0
+  version: 2.5.0
 platform: x64-mingw-ucrt
 authors:
 - David Heinemeier Hansson
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2024-04-08 00:00:00.000000000 Z
+date: 2024-04-27 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: railties
@@ -104,7 +104,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: 3.2.0
 requirements: []
-rubygems_version: 3.4.19
+rubygems_version: 3.5.9
 signing_key:
 specification_version: 4
 summary: Integrate Tailwind CSS with the asset pipeline in Rails.