Hey we might as well spill out all these wishes as the CSS feature train has been rolling and we oughta get while the getting is good.
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!
The reason I get so excited about watching and covering Interop around here is because it works so darn well. A browser ecosystem with different engines and different UX but supporting interoperable and standards based code keeps us employed and sane.
Little boosts of front-end development news, information, and advice — right to your feed reader of choice.
RSS
Brian Muenzenmeyer on new(ish) things in Node:
Through the efforts of contributors over several recent majors, great new features are landing. Each is useful in isolation, but put together they form a more and more comprehensive standard library.
Do you need a 3rd party testing library like jest? Maybe, but there is a tester built in now. Do you need a 3rd party file watcher like chokidar? Maybe, but there is a built-in watcher now. Do you need a build process to deal with TypeScript? Not anymore. Do you need chalk to colorize/style terminal output? Not anymore.
Bluesky is enjoying a boon in popularity. The API access right now is nicely open, allowing people to create some interesting stuff around it. I like this idea from Matt Kane: a Web Component (<bluesky-comments>) that loads up all the replies to any particular post like a comment thread. Imagine there is a post for every blog post you publish (like we do), instead of writing your own comment system you could just say “leave a reply on Bluesky” and that could be the whole commenting system. I hope get gets proper filtering.
Here's our page on guest writing. It's a win-win-win!
Frontend Masters Donates to open source projects. $363,806 contributed to date.