Rami

> FYI the next release will have a `configurePostCss` lifecycle, can be useful for Tailwind until we have first-class support > #4185 Any idea on a timeline for first-class support?

> @kvnxiao's solution is great! I just want to add an improvement to it. If you add the following to your `tailwind.config.js`: `important: '#tailwind',` then it will not affect the...

Experiencing the same thing, I'll post back here if I find a fix.

> If you are using `yarn`, a resolution defined in your `package.json` is a good workaround: > > ```json > "resolutions": { > "pg": "8.5.1" > } > ``` >...

I've been getting 9 but it's probably because my code is running in a Firebase cloud function.

I have this issue as well. It happens with TypeScript, not sure if it happens with JSX as well.

here is the link in webpack's docs. Apparently the err object does not contain the error so this repo needs to be updated. ``` webpack(config, (err, stats) => { if...

Created a PR above, hopefully he approves of it. There is an attached screenshot for the failed build error.


lol, do you realize that this PR goes back to the original upstream repository and not your personal one? I think you need to close this PR.