tailwindcss-rails 2.0.27 → 2.0.28

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6eafc52fc672910748ea21515fd8dbd5fe3e619f3d2c390dbe3e12dc6c787624
-  data.tar.gz: be900de0873368d10573df916256b41ac2120606dc7f93244880a22dcad94c1e
+  metadata.gz: 3a307f8be9bdfa07bdd137011c7c024d0ff35d1128743120f31ccedfe3a25381
+  data.tar.gz: eeb6976a023147b030985b3247b279ec4ea0812aa6433eb0c76c7689c2abd893
 SHA512:
-  metadata.gz: 7be21772157fa028a548f5fd3164368bb173443f7b180839637445eec344106b8345306f80e11aec01680601bb86051b35ae30289ea710150fc93e184058b4ad
-  data.tar.gz: d3a300da30322ee0a54884b3da92f3a7b091c6a461e7b436f7d0badc4c3b0aeebf0a24e48c01d277133b77076355ae41b14bb767a8e765fd9230e0c5b10031d2
+  metadata.gz: fcf8b9d62ba7030f36b473e6c3dde74c1a1058e52a6b616bc432a6993b79fa92634f2235422d5e08ad5da817edd738943e5a50a4316671c7c899ab71cc2ab1b7
+  data.tar.gz: 81b39111d0bab1151ee2a116d7a50a9249fca4edfd2bafea65409e876268dc769bc2172de52557658225bdd8644e51c24f562c48363461a4594b0edf20790c3d

data/README.md

@@ -70,9 +70,11 @@ While you're developing your application, you want to run Tailwind in "watch" mo
 - running `rails tailwindcss:watch` as a separate process,
 - or by running `./bin/dev` which uses [foreman](https://github.com/ddollar/foreman) to start both the Tailwind watch process and the rails server in development mode.
 
+If you are running `rails tailwindcss:watch` on a system that doesn't fully support file system events, pass a `poll` argument to the task to instruct tailwindcss to instead use polling: `rails tailwindcss:watch[poll]`. If you use `bin/dev` then you should modify your `Procfile.dev`.
+
 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.
 
-If you are running `rails tailwindcss:watch` on a system that doesn't fully support file system events, pass a `poll` argument to the task to instruct tailwindcss to instead use polling: `rails tailwindcss:watch[poll]`. If you use `bin/dev` then you should modify your `Procfile.dev`.
+If you are running `rails tailwindcss:watch` in a docker container without a tty, pass the `always` argument to the task to instruct tailwindcss to keep the watcher alive even when `stdin` is closed: `rails tailwindcss:watch[always]`. If you use `bin/dev` then you should modify your `Procfile.dev`.
 
 
 ### Debugging with unminified assets

data/lib/tailwindcss/commands.rb

@@ -83,9 +83,10 @@ module Tailwindcss
         end
       end
 
-      def watch_command(poll: false, **kwargs)
+      def watch_command(always: false, poll: false, **kwargs)
         compile_command(**kwargs).tap do |command|
           command << "-w"
+          command << "always" if always
           command << "-p" if poll
         end
       end

data/lib/tailwindcss/version.rb

@@ -1,3 +1,3 @@
 module Tailwindcss
-  VERSION = "2.0.27"
+  VERSION = "2.0.28"
 end

data/lib/tasks/build.rake

@@ -11,7 +11,8 @@ namespace :tailwindcss do
   task watch: :environment do |_, args|
     debug = args.extras.include?("debug")
     poll = args.extras.include?("poll")
-    command = Tailwindcss::Commands.watch_command(debug: debug, poll: poll)
+    always = args.extras.include?("always")
+    command = Tailwindcss::Commands.watch_command(always: always, debug: debug, poll: poll)
     puts command.inspect if args.extras.include?("verbose")
     system(*command)
   end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: tailwindcss-rails
 version: !ruby/object:Gem::Version
-  version: 2.0.27
+  version: 2.0.28
 platform: ruby
 authors:
 - David Heinemeier Hansson
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2023-04-02 00:00:00.000000000 Z
+date: 2023-04-21 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: railties