# Sage Tailwind multiple ruleset error

**URL:** https://discourse.roots.io/t/sage-tailwind-multiple-ruleset-error/12694
**Category:** sage
**Tags:** webpack
**Created:** 2018-06-14T15:13:31Z
**Posts:** 7
**Showing post:** 6 of 7

## Post 6 by @knowler — 2018-06-14T15:31:53Z

> [@gomako](#):
>
> I am also getting the following warning:
> 
> ```
> resolve-url-loader cannot operate: CSS error
> missing '}'
> ```

Within [the guide](https://roots.io/guides/how-to-setup-tailwind-css-in-sage/) I’ve written about setting up Tailwind in Sage, I have a footnote explaining that error:

> [@Using Tailwind CSS with Sage 9 + Webpack](https://discourse.roots.io/t/using-tailwind-css-with-sage-9-webpack/11330/8):
>
> 1 You will notice a Webpack warning when running `yarn start` . There is nothing going wrong with the compiling of your styles, but this is [a known issue](https://github.com/bholloway/resolve-url-loader/issues/28) with the `resolve url` Webpack loader. If you [comment it out in the Webpack config file](https://github.com/roots/sage/blob/808e37a0855e4ec9eb7176987dd09b5953676cb3/resources/assets/build/webpack.config.js#L91), the error will no longer appear, however, an error will persist in the browser console since this breaks source maps. Since you are using Tailwind — which generates CSS via a JavaScript config file — you don’t really need source maps, so you can go even further and remove the `sourceMap` option form the `css/postcss/sass` loaders. It does suck, but using a utility CSS framework you’ll notice you will be spending a lot less time in your stylesheets and more time in the markup designing.

---

_[View the full topic](https://discourse.roots.io/t/sage-tailwind-multiple-ruleset-error/12694)._