better error tolerance of wrong css rule

[hardfist]

I seems parcel-css will throw all the rule following unsupport rule

h1(>h1) {
  color: red;
}

div {
  color: blue;
}

the correct rule

div {
 color: blue
}

should be preserved but is discarded by parcel-css

and maybe the wrong rule should be preserved even it's recognized by compiler( which may be recognized by future browser for new css feature)

h1(>h1){
  color: red;
}

[devongovett]

Throwing errors on syntax errors is a useful feature for developers, so that we avoid shipping invalid code to prod. Why would you want to silently ignore/preserve these?

[hardfist]

because we want to migrate css to parcel-css which may contains invalid rule，but works on browser（browser just disard bad css rule and keep good css rule)

[devongovett]

Why would you not fix the bad code? If it isn't applying in the browser then why would you keep it? Isn't that just extra bytes to send?

[hardfist]

it may exists in other third party library which i cant modify or it maybe handled by other tools

[hardfist]

and it is more compatible with postcss

[devongovett]

As of the above commit, there is a new errorRecovery option which can be enabled. This ignores invalid rules and declarations rather than erroring (just like a browser would). They are omitted from the output, and a warning is emitted instead. Once this is released, I will work on exposing it as a config option in Parcel as well. Hopefully this allows people to work around issues in libraries more easily.