You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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 thepostcss-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.The text was updated successfully, but these errors were encountered: