Skip to content

CLI --content option shows warning #7210

@EatonZ

Description

@EatonZ

What version of Tailwind CSS are you using?

v3.0.16

What version of Node.js are you using?

v17.4.0

What operating system are you using?

Windows 11

Reproduction

Sample Download Link

  1. Use npm to run css-build-dev in package.json, preferably on Windows.
  2. Observe the warning.

Describe your issue

Tailwind v3.0 deprecated the CLI's --purge option and replaced it with --content. That's fine, but it doesn't work. I get the following:

warn - The `content` option in your Tailwind CSS configuration is missing or empty.
warn - Configure your content sources or your generated CSS will be missing styles.
warn - https://tailwindcss.com/docs/content-configuration

The issue can indeed be solved by adding content to tailwind.config.js, but since the option still exists in the CLI, it should also be possible there. Important to note is that --purge using the CLI worked fine in v2.x. There is clearly a bug with the new replacement --content option.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions