tailwindcss-rails 2.4.0-x86_64-linux → 2.5.0-x86_64-linux

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c4e697666ed8ab17e915f8fabde1d62fef07122493b61277dbc363e0c2818d5e
-  data.tar.gz: 6bea597750ba3c89ea1e61d39a9494f0cb2f0f980a97fe4f35ae378f06be02fc
+  metadata.gz: b1642cecf2c21ce0e1db964e82897394e5c5ae6848e5d58ba0f43c5015ed8e01
+  data.tar.gz: a380f67b43c7d4174994a7bde0c8a2850c24fe53a50ab85ff65f6749d4a4b167
 SHA512:
-  metadata.gz: fe00cfeedf3c088e829e9e173a11802a45aa91fef056cbfd9097af4637b06535001ef9b38cce76e4eebd27e29da46a510aaac55370db1aa67bd9ea146a4c17f1
-  data.tar.gz: 314732cfe0de085e529bc1edd5b5fbc612959e201b8ed5f0d63cccc63c1e0574144126cc61f88ed2fe0b6784dc7009d1b39d7d640df58927e7f49cfe270f201a
+  metadata.gz: 3911f0954387335c0d7ec70d822c024bbb3d0f3d07560ebe0c8955632da409b960ec5492aa41665a75a688ccde0bd6a57021c3a7dc51680409e729a1224a0e4e
+  data.tar.gz: 6ac44165be19133118d69ecef194b2412fa850ab4dceb187e3cdeb146a64eca7ca2936be0c8df5ba1d83074635979ce588128bed448e679f80dd05b533e3c5d2

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: x86_64-linux
 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.