doc: update README with TailwindCSS v4 upgrade instructions #480
Conversation
README.md
Outdated
| ```js | ||
| content: [ | ||
| '../public/*.html', | ||
| '../app/helpers/**/*.rb', | ||
| '../app/javascript/**/*.js', | ||
| '../app/views/**/*.{erb,haml,html,slim}' | ||
| ], | ||
| ``` | ||
| (Just add an additional ``.`` to all the paths referenced) |
There was a problem hiding this comment.
I mentioned this in the Discussions thread, but I think this is a bug that should be reported upstream. If you have a clean repro, would you please report that the path is being interpreted as relative to the config file in the upgrade tool (and not CWD as the CLI correctly does)?
There was a problem hiding this comment.
I'm sorry to have to ask, but I'm probably not going to have the time today to start to investigate and build a repro from scratch today.
There was a problem hiding this comment.
I'll see what I can find
README.md
Outdated
| # Gemfile | ||
| gem "tailwindcss-rails", "~> 4.0" # which transitively pins tailwindcss-ruby to v4 | ||
| ``` | ||
| To replace the class names accordingly for v4, go to ``config/tailwind.config.js`` update the ``content`` part to: |
There was a problem hiding this comment.
I would like to call this section out as a separate section in the doc. Some people may not care about upgrading their class names, especially if it's difficult (which this process surely will be for a large number of people).
There was a problem hiding this comment.
Also if (when?) we automate this in the tailwindcss:upgrade task we can more easily remove the section later.
There was a problem hiding this comment.
addressed at ffe7178
Co-authored-by: Mike Dalessio <[email protected]>
flavorjones
force-pushed
the
readme-update
branch
from
ffe7178 to
787bf26
Compare
No description provided.