If css containes a style without semicolon, building fails

[constgen]

Try to put background image as a last style in a rule but without a semicolon delimiter. This is valid CSS. The last semicolon is optional in the last line of the CSS rule. But this brakes building with react-scoped-styles. The issue doesn't apear if semicolon is always present. Can't be reproduced if the last line doesn't contain url(...) function.

Seems like an issue with regular expression.

[nairinarinyan]

Is there a specific reason not to put a semicolon in the end of the declaration? Or it's just a matter of preference?

Testing for presence of semicolon to figure out if it's a selector or declaration is the easiest. Because we assume that if you use preprocessor it will output a valid css with semicolons. E.g in some build configs resulting css selectors are split into multiple lines which means we can't test for {. And if you have
opacity: .5, you can't easily know if it's declaration or selector. So I think keeping it simple and generic enough is the way to go.

[constgen]

It should be possible to not put semicolon as it is valid CSS. Specs says that is is not a "line end"
but "delimiter" between properties.

I think the origin of this issue produces also the bug below.

Source

Result

padding is broken, but line-height is not. I experimented with these properties but padding always stay broken. Don't know why.

[Flcwl]

how deal with it?