Skip to content

v4: tailwindcss:watch not working after using the upgrade tool #475

@drale2k

Description

@drale2k

As mentioned in #450 (comment), the tailwindcss:watch command is no longer working for me after the upgrade to v4. The cause is having the @config directive present in the application.tailwind.css file used for backwards compatibility - as mentioned here #450 (reply in thread)

Everything seems to work after i removed it but i believe the upgrade script automatically added both lines to application.tailwind.css:

@import 'tailwindcss'; @config '../../../config/tailwind.config.js'; 
23:30:53 web.1 | => Booting Puma 23:30:53 web.1 | => Rails 8.0.1 application starting in development 23:30:53 web.1 | => Run `bin/rails server --help` for more startup options 23:30:53 web.1 | Puma starting in single mode... 23:30:53 web.1 | * Puma version: 6.5.0 ("Sky's Version") 23:30:53 web.1 | * Ruby version: ruby 3.4.1 (2024-12-25 revision 48d4efcb85) +YJIT +PRISM [arm64-darwin24] 23:30:53 web.1 | * Min threads: 3 23:30:53 web.1 | * Max threads: 3 23:30:53 web.1 | * Environment: development 23:30:53 web.1 | * PID: 43869 23:30:53 web.1 | * Listening on http://127.0.0.1:3000 23:30:53 web.1 | * Listening on http://[::1]:3000 23:30:53 web.1 | Use Ctrl-C to stop 23:30:53 worker.1 | 23:30:53 worker.1 | [GoodJob] [43871] GoodJob 4.8.0 started scheduler with queues=fast max_threads=3. 23:30:53 worker.1 | [GoodJob] [43871] GoodJob 4.8.0 started scheduler with queues=default,fast max_threads=5. 23:30:53 worker.1 | [GoodJob] [43871] GoodJob 4.8.0 started scheduler with queues=* max_threads=5. 23:30:53 worker.1 | [GoodJob] GoodJob started cron with 2 jobs. 23:30:53 worker.1 | [GoodJob] Notifier subscribed with LISTEN 23:30:54 css.1 | exited with code 0 23:30:54 system | sending SIGTERM to all processes 23:30:54 web.1 | - Gracefully stopping, waiting for requests to finish 23:30:54 web.1 | Exiting 23:30:54 web.1 | terminated by SIGTERM 23:30:55 web.1 | exited with code 0 

I am not sure yet if removing the old config has any side effects and how it affects the plugins loaded through the config.

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-more-infoFurther information is needed to unblock

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions