tailwindcss-rails 2.4.0-arm-linux → 2.5.0-arm-linux

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7f664267f48e78b2489ce10c9a66484f3e723dffe011fea92de93a3e2481c02a
-  data.tar.gz: abdf04060b080b735116e7d46ad8fb1656818ad5338d95e65aea7fdbab53b8df
+  metadata.gz: aec6a6589a5529a562065a5a39ed72b2c994c40462aeb8342aa631443ae27a32
+  data.tar.gz: b1787d32ff51fa39e580b4379b1a3df92de7f92d155a88ce122a810382f98f6e
 SHA512:
-  metadata.gz: 7063afddba3cd16832117fef14e8f5280c188a09fefe5b67eaa9f98cbed6379875ada6f443df9c7378c87fb4e25c5927a140446c8ee4c5ff2c27f50bd0406858
-  data.tar.gz: d61027741f09d1d4bf87da90409e0a8610acbb83e0de0b23d1628e5d448efa18a36b29b2b1986796741579ecadddacdafee59fed2abf4a31312257311bf73905
+  metadata.gz: 4cb943277270a7c1ee77d8c85d29073f01dc6b23d256a4c32bf443169475a7dadc46c772faac4b26a5ff4c343384855aeb23f1003f3af36aa8a399238cc93f37
+  data.tar.gz: 876c61cb9d4a8d7905c99d63f9ca10975ec70eecc6156a14a72df55a9f4d96cdbe03c690ac4090e81d6ca78395ee5ed4df799bf40c29c703abf2df3b5033b0f9

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: arm-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.