fix(tailwindcss): fix TailwindCSS pack not loading when using tailwindcss-rails Ruby Gem

[natematykiewicz]

📑 Description

#912 caused the Tailwind LSP to not work, when using the tailwindcss-rails Ruby gem.

The tailwindcss-rails Ruby gem keeps the config at config/tailwind.config.js, which is not in the new root_dir config.

https://github.com/rails/tailwindcss-rails?tab=readme-ov-file#configuration-and-commands

[github-actions]

Review Checklist

Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:

Proper conventional commit scoping:

• If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin

• If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error

• Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above

• README is properly formatted and uses fenced in links with <url> unless they are inside a [title](url)

• Proper usage of opts table rather than setting things up with the config function.

[mehalter]

LGTM!

[rafaelderolez]

Sorry about that!

This actually made me go look at the docs and it seems custom config location and names are supported: https://tailwindcss.com/docs/configuration#using-a-different-file-name.

We could consider adding a statement to check package.json for a tailwindcss key, and the equivalent for Ruby projects (and others?).

Thoughts? @mehalter @natematykiewicz

[natematykiewicz]

No problem. I sort of wish they didn’t change the default location of the config. But I also get it, every other Rails config is in the config directory.

The Ruby gem doesn’t use package.json. It includes a compiled executable and some Ruby config. It actually exists for Rails apps that want to use Tailwind but have no other need for NodeJS.

[natematykiewicz]

FWIW, the official Tailwind guides mention this config file.

https://tailwindcss.com/docs/guides/ruby-on-rails

[treshenry]

And... Elixir Phoenix projects put the tailwind config at assets/tailwind.config.js. https://github.com/phoenixframework/tailwind

Could not figure out what broke, and had to go digging. 🤷‍♂️ I'll put up a PR shortly.