-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document upgrade path for --config
CLI option
#2041
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
6920b4a
to
a45cd53
Compare
In v3, you could use the `--config` option to point to your configuration file. | ||
In v4 there is no configuration file anymore. If you still require a | ||
configuration file, make sure to include it in your CSS file and use the `@config` directive: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think about something like this? (probably still needs to be split across multiple lines tho)
In v3, you could use the `--config` option to point to your configuration file. | |
In v4 there is no configuration file anymore. If you still require a | |
configuration file, make sure to include it in your CSS file and use the `@config` directive: | |
In v3, you could use the `--config` option to point to your configuration file. Now that projects are configured via CSS this option is no longer available. For projects that require a configuration file for compatibility reasons, load the file by using the `@config` directive in your CSS: |
|
||
```shell | ||
npx @tailwindcss/cli -i input.css -o output.css | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should you include the config file content as an example code block too?
This PR updates the upgrade guide for when you are using the Tailwind CLI with the
--config
option.This option doesn't exist anymore, and instead you should use the
@config
directive in your CSS.