Support for reporting CSSSyntaxError?

We're trying to integrate `stylelint` into a project in our org which uses `lit-html`. I've noticed that for `postcss-lit`, whenever there is a CSSSyntaxError from `postcss` parsing, it will entirely opt to "skip" the template, and not report back to the user the specific error.

Will presenting the details of the CSSSyntaxError to the user something that can be considered?

For example:

```js
class MyCustomELement {
static styles = css`
.icon {
width: 40px;
height: 40px;

.card {
display: flex
}
`
}
```

The code above will cause a `CSSSyntaxError` due to a missing closing bracket for the `icon` selector.

With `postcss-lit`, it will show a warning in the console, with a recommendation to ignore the template. On a conventional linting flow, it usually will report back to the user that there is a syntax error with details like:

```bash
my-custom-element.js
64:3 Unclosed block CSSSyntaxError
```

The details can be derived from the `Error` object thrown by postcss