tailwindcss-rails 2.4.0-x86_64-darwin → 2.5.0-x86_64-darwin

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 424105d7e5f2250d2af540a59b6f7fb11c357e4262bc5d4e0686f0af607a1398
-  data.tar.gz: 67c63db4540474f6c0c07bf405fcc519a82d91b646d9f0dfb2fb29cf8da9292a
+  metadata.gz: 17c1e1830dfad63a90e03fae6c349875616902978f4e324f0ec8f95f62855a72
+  data.tar.gz: 55d5ece45e0871d79aedc94fbed73954c7fff77fb967cd97cd62c86bb7bd6ab8
 SHA512:
-  metadata.gz: a1c952d3a69f7a0c2993b79e9e3f7d7e44df0c0bdebfe8158b08788853cc132a5a55c341537d5051cea82ee816f18c3c1087569ac823f2760a44c30e2c979d88
-  data.tar.gz: 7faa6f79a79002f586f121870d75b15e8196d0c24892e9f4342c42c87cb778202eb36321fe4da14c8c20f550a2b045082ad2716d97c8dd1622b35fb58ab73380
+  metadata.gz: ea0f506b3d15afbefadbd5a8b899aa5358388b048e33197fc1a0735c5a99c8a1d44dc09e3a428227eb057d2859523dff797b9f05886b75def548723cb14b33dc
+  data.tar.gz: 3560285c67e7494aeb8e322043a4247cd903c7a45b74d95d54d53f51c16dfaea342a90141b6fce004255898573b0900d3bb8a5bea4a44a5b8746a24193da80a5

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-darwin
 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.