Philipp Spiess 7be5346e2e

Ensure upgrade tool has access to a JS config (#14597) ...

In order to properly migrate your Tailwind CSS v3 project to v4, we need
access to the JavaScript configuration object. This was previously only
required for template migrations, but in this PR we're making it so that
this is also a prerequisite of the CSS migrations. This is because some
migrations, like `@apply`, also need to convert candidates that to the
v4 syntax and we need the full config in order to properly validate
them.

In addition to requiring a JS config, we also now attempt to
automatically find the right configuration file inside the current
working directory. This is now matching the behavior of the Tailwind CSS
v3 CLI where it will find the config automatically if it's in the
current directory and called `tailwind.conf.js`.

---------

Co-authored-by: Robin Malfait <malfait.robin@gmail.com>

2024-10-07 18:02:28 +02:00

..

cli

Fix rebuilds when editing imported CSS files (#14561)

2024-10-01 11:52:12 +00:00

postcss

Improve @tailwindcss/postcss performance for initial builds (#14565)

2024-10-03 16:21:54 +02:00

upgrade

Ensure upgrade tool has access to a JS config (#14597)

2024-10-07 18:02:28 +02:00

vite

Add integration tests for multi-root builds (#14564)

2024-10-01 17:00:20 +02:00

package.json

Add integration test setup and tests for the Vite integration (#14089)

2024-08-02 11:50:49 +02:00

utils.ts

Only run Ubuntu tests on feature branches (#14560)

2024-10-01 13:45:52 +02:00