HiDeoo

@hideoo.dev

Mostly TypeScript, Astro, and things like React or Rust — @astro.build core maintainer https://hideoo.dev

🎉 Introducing npmchart.com Analyze npm packages (downloads, releases), Github activity (releases, stars, commits, issues, PRs), compare packages, user pages, download or copy any charts, and more!

BildBildBildBild

To target multiple classes with the same prefix, you'd typically have to resort to brittle attribute selectors. To make things easier, CSS is getting a new selector: the “Class Prefix Selector” (`.foo-*`). Check brm.us/class-prefix... to get the details. (Browser Support: None 😛 — just resolved!)

The Future of CSS: Target Multiple Classes with the Class Prefix Selector

To target multiple classes that share the same prefix, you'd typically have to resort to brittle attribute selectors or add extra base classes to your markup. To make things easier, CSS is getting a n...

brm.us

astro-lilypond@0.16.1 now exports proper TypeScript types for Astro content collections, which should make it easier to access and display metadata from your `.ly` files 🎶

A typeahead showing TypeScript fields which exist on `score.data.meta`, including "arranger", "composer", "copyright", "dedication", "instrument", "meter", "opus", "piece", and "poet"

🌿 A new version of the Web Sustainability Guidelines is out! www.w3.org/TR/web-susta... Updates include: - Impact Measurement + Impact API - Lots of small tweaks following peer review - Improved tone of voice and readability, new introduction Changelog: github.com/w3c/sustaina...

Web Sustainability Guidelines (WSG)

Web Sustainability Guidelines (WSG) provide actionable recommendations to help digital teams make informed, sustainable decisions. In considering different aspects of work and the web, these guideline...

w3.org

Say hello to 🐣 fledgling - a new tool to create new npm packages and setup/sync trusted publishing (OIDC) settings. Works great for one offs, but even better in a monorepo! just `npx fledgling`

Watch out! Chrome has a huge bug with <input type="number"> which causes values to change unexpectedly. It's fixed in Chrome 150, but that won't land until the end of June.