Alex Sherwin

MDN has some details about the flexible varaitions that the CSS [`url()`](https://developer.mozilla.org/en-US/docs/Web/CSS/url) supports. Based on the description and some googling, I'm not sure that this formal spec can be succinctly...

I’ve played with bringing in [lightningcss](https://github.com/parcel-bundler/lightningcss) and using a url visitor to aggregate all valid urls in a font face rule instead of the URL_RE behavior I believe it works...

Using lightningcss to parse the @font-face rules definitely works, however, it would be in a stricter, more standards compliant way. This means potential behavioral differences to how this library currently...

This may be a good regex to use for the `URL_RE` in lieu of using a full blown CSS AST parser: ``` url\((?:(?:"((?:\\.|[^"\\])*)")|(?:'((?:\\.|[^'\\])*)')|((?:[^'")\\]*(?:\\.[^'")\\]*)*)))\) ``` Seems to work reasonably well and...

> (stupid suggestion: use numerical contraction "o14m") [Nerd sniped](https://en.wikipedia.org/wiki/Numeronym) ... o3s4p5 ?

Maybe it would introduce too much burden but… slightly crazy idea, it could be beneficial to try and support two renderering options to ensure the core doesn’t make accidental choices...

@Semigradsky it seems the current *@types/uuid* still allows the following (**now invalid**) import syntax to compile (using the default export): ```typescript import uuid from "uuid"; ``` But as of uuid...

Hi @Semigradsky, You're absolutely right, turns out it's because we have (and have had since forever) tsconfig option `allowSyntheticDefaultImports` enabled. Having this enabled is probably pretty commonplace, it stems from...