Skip to content
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

Not all postcss configuration options are supported using the tailwind CLI #7856

Closed
rbclark opened this issue Mar 15, 2022 · 2 comments · Fixed by #8226
Closed

Not all postcss configuration options are supported using the tailwind CLI #7856

rbclark opened this issue Mar 15, 2022 · 2 comments · Fixed by #8226
Assignees

Comments

@rbclark
Copy link

rbclark commented Mar 15, 2022

What version of Tailwind CSS are you using?

For example: v3.0.23

What build tool (or framework if it abstracts the build tool) are you using?

For example: tailwind-cli v3.0.2.3 directly

What version of Node.js are you using?

For example: v17.7.1

What browser are you using?

N/A

What operating system are you using?

macOS

Reproduction URL

https://gist.github.com/rbclark/71a0425496cdb5b662627704576ad276

Describe your issue

No matter what options I pass into the map option, they are not respected. When doing the exact same thing though the postcss-cli the options are respected. In my case I am running into an issue where one of my files has an external sourcemap and it is forcing all of my sourcemaps to be generated externally. Switching to the postcss CLI with the exact same config fixed the problem which makes me think it is a problem with the tailwind CLI.

@rbclark
Copy link
Author

rbclark commented Apr 28, 2022

Thanks @thecrypticace!

@thecrypticace
Copy link
Contributor

thecrypticace commented Apr 28, 2022

Hey, good catch! Yeah we were only loading the plugins from the config file and not passing options through from the config file. The fix for this should hit our insiders build in a few minutes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants