tailwindcss-rails 2.4.0-arm64-darwin → 2.5.0-arm64-darwin

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 5bc5b4915801a207881612b07769292ed7b441769007f613c83d06ee4724a085
-  data.tar.gz: 6f1ecc4c0ed4b12a8cbd9d1a8c1a9918c34ac7c2e038b5e32f2b605bfbe2e3f5
+  metadata.gz: 88bd9a5cf41a788f1839325fdd08e269c6d5fdcf51f95db13559c95c6d7fbd31
+  data.tar.gz: da4a3b82f92830cb69aedf6eb537d2348349c45c0c5f02f04be059efe0cea6d4
 SHA512:
-  metadata.gz: 5fcb6015d610702a65655ca65449fc08675492ae477e5260844763bb49f455105b81064030c4de448f636b0b4196f2f2238e70d69d819f446580d52e7564aa86
-  data.tar.gz: 5cb6fd815921fa17edc677f621a3a8506dde094001a16394f6623477c480bbc3853867f4ca3fe4ac410ea3b416072d8b00a7cc9a0cc816281d83fa0595cd1b4c
+  metadata.gz: 4dd3a604509511af1d5e76915ff071c41384638e5f0e7bb46831aede62bc81f0c1c86c646d7448d9263f7097fb2f7863b1ba0b50fb04108811f8df728f726f34
+  data.tar.gz: 3b98b98ffba5f83f73a4dad1322260cea430839d39cac92de42944ce5bbd254820df0d3c662b1f2893a366306b181a2baf1f5a3a9ca17a9776aaaad6b3d46f6c

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