tailwindcss-rails 2.4.0-x64-mingw32 → 2.5.0-x64-mingw32

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7fd886520468547e55ca3d52aa20d36ee1624a6787708500ab72e8b53e6846f7
-  data.tar.gz: 930405245e6e50b245c6bfd791c3826265a9ad0edd9f953038d7f97a0e81d93f
+  metadata.gz: 02cdc1fa59f7251aaed9801aec6ccb78c182ca865ddaef107cb48ee64c5c23b4
+  data.tar.gz: 05425a5d19dedc930e8bdc4e3c41f5f515d5267cfd4d2bf4cd92e5b5656152d3
 SHA512:
-  metadata.gz: 0d25cbfa80547e1f4e2af872302081b673de3db790b2550bd782a9f59c2bc7f3876fd6c20682e15c5adb4a6c73dd48f0603e145cb1be8568fd2d483a2a6da8d8
-  data.tar.gz: 9b70a236cbe1b062e9c818b92ff58fb09d22b175fce1e71cdefdb1798952c3cafabf433b725a0acb9a9e630eaacef9c2029ee9b11525a0265698e154d4b752c6
+  metadata.gz: f0fc060a0c974429c71e20822eaea398a31cc519e98007f36b4628dc350a16260bd49cec3ff03e4ff845334005692af684b16e09793c09c533240ce6c44d09e3
+  data.tar.gz: 94de63ccfcada1768d6c2742389354eb7d2c6e98cb56ac1a365502b7c853a6a423d77b486ccfb9968aa86aa763474be9141bf3740eaa3ea3a34b994bd14ea721

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: x64-mingw32
 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.