Set a variable in Pug, then create an inline script which sets that variable for using in JavaScript and use setProperty to pass it to CSS.

Accordion details, toggle switches, styleable selects, responsive video, and more!

If you’ve applied `container` to an element, know that, for the next little while, that makes a new “formatting context” in Safari, and does not in Chrome or Firefox.

You can build your own TypeScript build process, and you might want to if you need true type checking and compatibility with a wider ecosystem of tools. But lots of tools, including now Node itself, just accept TypeScript as if it were JavaScript.

Why can’t we see if a feature is polyfillable or able to be progressively enhanced in the baseline data? There are reasons.

It’s quite fun to have an element react to another element scrolling in an unexpected way!