tailwindcss-rails 2.4.0 → 2.4.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c6885977e39ac7e28580dc7296ff7eb89ae593ef5cce846a631b9f90c845f3d7
-  data.tar.gz: 6e5ddea98ed66a41d8c3c0575c5015f5cfa44703b8c91019831ac14ce04e4acb
+  metadata.gz: d6a824204deedd0ba3ea31433af0fc2e408c69a62704abb45b046cf009306b05
+  data.tar.gz: d00edd2a9ba2af767c244dfa881ca5f3fb8aec83cc8d1a07d94808e294381415
 SHA512:
-  metadata.gz: 538f8be7ff95b436605a828170ea87bba9629a3dfe4fe58598b420e1c4e816fbc768db2e3180c6a03e597b491439b8371e00a7792c096c48b41cf24740054d0e
-  data.tar.gz: ead1e73f8ae4bbfc3391be7a858f4c3c181780237eb78f56dae514c3c13590eedb01b7a04d55ce5efafcb33c3ae7ce8c992696919c3b9cec05c77d78c8a77879
+  metadata.gz: 5bf5ff0bcbc70ef0bb24241334300d0cefe8962d2749286be088b57e2bb38968e310745b24530ce599c162a22a0d3e58946b8ea2d69a70eb7f5cc451addb9a5b
+  data.tar.gz: 0d2adb6ff3f83b760346aaf91955e53ad3a72835a7b6adcbec39e8afb2588aa37b237ae4d12f3b575afff93366ccd446ffef03a9e9a06cff939fc418191014c1

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,17 @@ 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 `ruby/debug` with the Puma plugin
+
+If you are using the `ruby/debug` debugger while using the Puma plugin from this gem, and you're experiencing what looks like hanging or lost keystrokes, then you'll need to disable Reline.
+
+You can read the [`debug` documentation](https://github.com/ruby/debug?tab=readme-ov-file#configuration) for more information, but the easiest thing to do is to set the environment variable `RUBY_DEBUG_NO_RELINE`:
+
+``` sh
+RUBY_DEBUG_NO_RELINE=1 rails server
+```
+
+
 ### 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/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.4.1"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: tailwindcss-rails
 version: !ruby/object:Gem::Version
-  version: 2.4.0
+  version: 2.4.1
 platform: ruby
 authors:
 - David Heinemeier Hansson
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2024-04-08 00:00:00.000000000 Z
+date: 2024-04-25 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: railties
@@ -102,7 +102,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.