Manuel Strehl

In one repository I need to check in JS/CSS compilation results next to the source files. To get an idea of the changes in those compiled files I use this...

I was about to ask, if the regular expression to check for CSS files could be changed to something like `/.css($|\?)/` or `/^css:|\.css$/` (allowing for URLs like `css:/generated/style/sheet.php`) to match...

A similar project, [Toast](https://github.com/pyrsmk/toast), uses a `[css]` prefix. The Webpack [CSS loader](https://github.com/webpack/css-loader) uses the syntax `css-loader!./file.css`. Personally, I thought, that `css:` looks more "URL like" (like the `view-source:` pseudo-protocol of...

Thank you! I'll go trying it immediately.

Hi! Thanks for the detailed report! Oh, radio buttons again. These are the one type of input elements that need special casing all over the code base. I’ll take a...

`:dirty` is not completely equivalent to `.hf-validated`. The first should match all `value!=defaultValue` elements. The second matches every element, that was validated at least once.

1602dfe adds three more, 87c2724 another one.

`:optional` is not the same as `:not([required])`. The former matches only form elements, the latter any element (including `` and ``) without an attribute `required`.

Thank you for pointing this out! Yes, the `index.d.ts` file was indeed missing from the npm package. If you update to [email protected], it will be included. A word of warning:...

Thanks for the suggestion! No, it's not possible currently, but I toyed with that thought myself. Out of interest, how would your use case look like? (I.e., what would a...