You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I created a new Rails application (with v7.0.3.1) and generated a new system test.
With v2.0.11 of the tailwindcss-rails gem, bin/rails test:system prints the Tailwind CSS compilation output and exits (without running any tests).
If I downgrade to v2.0.10, it prints the Tailwind CSS compilation output and proceeds to run the tests.
I believe the use of exec (introduced in #181) has changed the behavior when multiple Rake tasks are involved as is the case when the test:prepare Rails Rake task is enhanced with tailwindcss:build. The process is exiting after the Tailwind CSS compilation.
The text was updated successfully, but these errors were encountered:
@chrisgibson Yup, what you're describing makes sense and we shouldn't be using exec. I'll explore replacing it putting some tests in place to prevent regressions in the rake tasks.
I created a new Rails application (with v7.0.3.1) and generated a new system test.
With v2.0.11 of the tailwindcss-rails gem,
bin/rails test:system
prints the Tailwind CSS compilation output and exits (without running any tests).If I downgrade to v2.0.10, it prints the Tailwind CSS compilation output and proceeds to run the tests.
I believe the use of
exec
(introduced in #181) has changed the behavior when multiple Rake tasks are involved as is the case when thetest:prepare
Rails Rake task is enhanced withtailwindcss:build
. The process is exiting after the Tailwind CSS compilation.The text was updated successfully, but these errors were encountered: