Due to all the streaming services, we had barely been using our DVDs and BluRays for a long time. So, to free up shelf space, we packed them away into boxes and put them in the loft.
Literally minutes later our broadband provider had an outage. No Netflix / Prime Video / Disney+ 🤦♂️
As one of the spec editors, I really love seeing support for the DTCG file format ( https://tr.designtokens.org/ ) appearing in tools. The dream of seamless interoperability for design tokens edges a step closer each time.
Started writing a decision log for our #DesignSystem. Documenting why we chose to build plain ol' #HTML and #CSS where we can and #WebComponents where client-side #JS is needed is turning into a bit of a manifesto. Essentially we're using (and encouraging others to use) #ProgressiveEnhancement 😉
Spent this afternoon wrangling NPM dependencies in our #DesignSystem's monorepo. Managed to nuke a few and also eliminate all the vulnerable package versions being reported by npm audit.
Grumble. #Angular is doing my head in. Why do Angular packages create a new package.json in the dist folder and expect you to cd into there before running npm publish?!?!
I have a monorepo with lots of other non-Angular packages. I use Changesets to manage versioning and releases.
Now, because Angular can't just use npm like it's meant to be used, I'm stuck.
Went down a rabbit hole today trying to share some CSS between a document (i.e. "light DOM") and the shadow DOMs of some #HTML custom elements (aka #WebComponents).