|
7 | 7 | <!-- toc -->
|
8 | 8 |
|
9 | 9 | - [Installation](#installation)
|
10 |
| - * [Choosing a specific version of `tailwindcss`](#choosing-a-specific-version-of-tailwindcss) |
11 |
| - * [Using a local installation of `tailwindcss`](#using-a-local-installation-of-tailwindcss) |
| 10 | + - [Choosing a specific version of `tailwindcss`](#choosing-a-specific-version-of-tailwindcss) |
| 11 | + - [Using a local installation of `tailwindcss`](#using-a-local-installation-of-tailwindcss) |
12 | 12 | - [Upgrading your application from Tailwind v3 to v4](#upgrading-your-application-from-tailwind-v3-to-v4)
|
13 |
| - * [You don't _have_ to upgrade](#you-dont-_have_-to-upgrade) |
14 |
| - * [Upgrade steps](#upgrade-steps) |
15 |
| - * [Troubleshooting a v4 upgrade](#troubleshooting-a-v4-upgrade) |
16 |
| - * [Updating CSS class names for v4](#updating-css-class-names-for-v4) |
| 13 | + - [You don't _have_ to upgrade](#you-dont-_have_-to-upgrade) |
| 14 | + - [Upgrade steps](#upgrade-steps) |
| 15 | + - [Troubleshooting a v4 upgrade](#troubleshooting-a-v4-upgrade) |
| 16 | + - [Updating CSS class names for v4](#updating-css-class-names-for-v4) |
17 | 17 | - [Developing with Tailwindcss](#developing-with-tailwindcss)
|
18 |
| - * [Configuration and commands](#configuration-and-commands) |
19 |
| - * [Building for production](#building-for-production) |
20 |
| - * [Building for testing](#building-for-testing) |
21 |
| - * [Building unminified assets](#building-unminified-assets) |
22 |
| - * [Live rebuild](#live-rebuild) |
23 |
| - * [Using Tailwind plugins](#using-tailwind-plugins) |
24 |
| - * [Using with PostCSS](#using-with-postcss) |
25 |
| - * [Custom inputs or outputs](#custom-inputs-or-outputs) |
26 |
| - * [Rails Engines support (Experimental)](#rails-engines-support-experimental) |
| 18 | + - [Configuration and commands](#configuration-and-commands) |
| 19 | + - [Building for production](#building-for-production) |
| 20 | + - [Building for testing](#building-for-testing) |
| 21 | + - [Building unminified assets](#building-unminified-assets) |
| 22 | + - [Live rebuild](#live-rebuild) |
| 23 | + - [Using Tailwind plugins](#using-tailwind-plugins) |
| 24 | + - [Using with PostCSS](#using-with-postcss) |
| 25 | + - [Custom inputs or outputs](#custom-inputs-or-outputs) |
| 26 | + - [Rails Engines support (Experimental)](#rails-engines-support-experimental) |
27 | 27 | - [Troubleshooting](#troubleshooting)
|
28 |
| - * [The `watch` command is hanging](#the-watch-command-is-hanging) |
29 |
| - * [Lost keystrokes or hanging when using terminal-based debugging tools (e.g. IRB, Pry, `ruby/debug`...etc.) with the Puma plugin](#lost-keystrokes-or-hanging-when-using-terminal-based-debugging-tools-eg-irb-pry-rubydebugetc-with-the-puma-plugin) |
30 |
| - * [Running in a docker container exits prematurely](#running-in-a-docker-container-exits-prematurely) |
31 |
| - * [Conflict with sassc-rails](#conflict-with-sassc-rails) |
32 |
| - * [Class names must be spelled out](#class-names-must-be-spelled-out) |
33 |
| - * [`ERROR: Cannot find the tailwindcss executable` for supported platform](#error-cannot-find-the-tailwindcss-executable-for-supported-platform) |
34 |
| - * [Using asset-pipeline assets](#using-asset-pipeline-assets) |
| 28 | + - [The `watch` command is hanging](#the-watch-command-is-hanging) |
| 29 | + - [Lost keystrokes or hanging when using terminal-based debugging tools (e.g. IRB, Pry, `ruby/debug`...etc.) with the Puma plugin](#lost-keystrokes-or-hanging-when-using-terminal-based-debugging-tools-eg-irb-pry-rubydebugetc-with-the-puma-plugin) |
| 30 | + - [Running in a docker container exits prematurely](#running-in-a-docker-container-exits-prematurely) |
| 31 | + - [Conflict with sassc-rails](#conflict-with-sassc-rails) |
| 32 | + - [Class names must be spelled out](#class-names-must-be-spelled-out) |
| 33 | + - [`ERROR: Cannot find the tailwindcss executable` for supported platform](#error-cannot-find-the-tailwindcss-executable-for-supported-platform) |
| 34 | + - [Using asset-pipeline assets](#using-asset-pipeline-assets) |
35 | 35 | - [License](#license)
|
36 | 36 |
|
37 | 37 | <!-- tocstop -->
|
@@ -99,7 +99,7 @@ gem "tailwindcss-ruby", "~> 3.4" # only necessary with tailwindcss-rails <= 3.3.
|
99 | 99 | First, update to `tailwindcss-rails` v4.0.0 or higher. This will also ensure you're transitively depending on `tailwindcss-ruby` v4.
|
100 | 100 |
|
101 | 101 | ```ruby
|
102 |
| -# Gemfile |
| 102 | +# Gemfile |
103 | 103 | gem "tailwindcss-rails", "~> 4.0" # which transitively pins tailwindcss-ruby to v4
|
104 | 104 | ```
|
105 | 105 |
|
@@ -392,7 +392,7 @@ If you need to use a custom input or output file, you can run `bundle exec tailw
|
392 | 392 |
|
393 | 393 | _This feature is experimental and may change in the future. If you have feedback, please join the [discussion](https://github.com/rails/tailwindcss-rails/discussions/355)._
|
394 | 394 |
|
395 |
| -If you have Rails Engines in your application that use Tailwind CSS and provide an `app/assets/tailwind/<engine_name>/engine.css` file, entry point files will be created for each of them in `app/assets/builds/tailwind/<engine_name>.css` on the first build/watch invocation so they can be included in your host application's Tailwind CSS by adding `@import "../builds/tailwind/<engine_name>"` to your `app/assets/tailwind/application.css` file. |
| 395 | +If you have Rails Engines in your application that use Tailwind CSS and provide an `app/assets/tailwind/<engine_name>/engine.css` file, entry point files will be created for each of them in `app/assets/builds/tailwind/<engine_name>.css` on the first build/watch invocation or manual call for `rails tailwindcss:engines` so they can be included in your host application's Tailwind CSS by adding `@import "../builds/tailwind/<engine_name>"` to your `app/assets/tailwind/application.css` file. |
396 | 396 |
|
397 | 397 | > [!IMPORTANT]
|
398 | 398 | > You must `@import` the engine CSS files in your `app/assets/tailwind/application.css` for the engine to be included in the build. By default, no engine CSS files are imported, and you must opt-in to using the file in your build.
|
|
0 commit comments