Make that 3 mentions in 2 weeks! 🤪

oooohhh found a way to makes @bram.us/specificity AST-agnostic 😮 -> add possibility to calculate specificity for either postcss nodes, csstree or any other parser (as long as you write a small adapter around the AST) which brings me to the next idea...

Has anyone written a good guide on renaming/rebranding an npm package? I want my color-sorter package to be namespaced, so it'll become `@projectwallace/color-sorter`. Any steps I must not forget?

somehow I missed this awesome report about CSS usage from @projectwallace.com Definitely worth checking out! www.projectwallace.com/the-css-sele...

Two mentions from @syntax.fm in one week! You guyssss... ✌️ Episode 999 is all about writing maintainable CSS. You _bet_ Project Wallace is your Swiss army knife for that!

Just 20-ish more lint rules. Then I'll call it beta. Just 30 more. It'll be ready, for sure. Just 40...

me: play 90's female artist playlist spotify: so 5 songs is enough, right? I'll play dog shit like Bon Jovi next and only male artists from now on

Dogfooding my stylelint plugin pack on projectwallace itself. And it's CSS is not even AI generated. Just imagine!

In my previous job I would constantly tell this: if you care enough, make it a lint rule. Otherwise just move on with the stuff that actually matters.

CSS shorthands mannnnnnnn...

Maybe today is a good day to update my official title to *webmaster* of Project Wallace. The time feels right.

Cascading Style Shirts dot com

I'll be fanboy-ing *so* hard over this year's CSS Day! 😍

We make good use of the Intl API in our app and on our website, so it was high time we did a Polypane-style deep-dive on it. Check out our new article, play around with the interactive examples or hear Kilian yap about it on video. Whatever works for you! polypane.app/blog/the-int...

Ooh, just realised I can incorporate the wallace stylelint plugin with existing pages on the website. This also sort of clears the way for the css-analyzer to be a more un-opinionated analyzer and the linter for flagging issues. Still, the analyzer can expose tons of little functions to do analysis.

Happy New Taskmaster Series to all who celebrate!

Wait, we can drop format_bytes??? www.stefanjudis.com/today-i-lear... via @stefanjudis.com

This week's Web Weekly is about to hit all the inboxes in just a moment! 🫣 If you're into web dev news close to the platform (you know, browser features, specs, and all the good stuff), you should check it out! https://webweekly.email/...

Added a metadata message to the css coverage reporter to get a feel for performance and it's cool and I saw the OXC folks do it. Had no idea that my own playwright suite would generate 4000+ JSON files. Well. It doesn't. There a bug somewhere, there were 'only' 247 (=== # of tests). Still cool!

Seriously, I can't publish any of my packages anymore. What's going on? `npm install -g npm` fails, and removing it ends up with a 404 error during `npm publish` 😭

Trusted publishing is great, of course. But now Github Actions breaks on `npm i -g npm` so my releases can't run...

It finally clicked. My (experimental) CSS parser uses 1 object type under the hood to prevent polymorphism (==fast) but the DX is really bad. Now overlaying the whole thing with extra subclassed types: better DX, zero runtime overhead! Install size does increase a but, but we're still below 200kB 😇

so done with rounded corners. give me pointy corners. give me razor-sharp "wear a glove before you press it" corners.

I never do April Fools. Except that one time where we spent hours bypassing our own, very strict CSP to inject a little bit of JS on our website. It added a "pay lots of bitcoin now to get your site back", but only for our company's internal IP. Had it taken down in 3 minutes because PANIC!!

April Fools would have extra fun and chaos if everyone would write extra validation errors in their stylelint/eslint plugins that generate new errors on each run.

Lolololol, props to @nerdy.dev for rocking this shirt in the wild. Just stumbled upon a @whiskey.fm episode from last year www.youtube.com/live/je_Gj7K... Yes, your chant was the inspiration for the shirt; that's why I wanted you to have one! Need to design and have new ones printed though.

Spotify really needs a "play last in queue". Current behaviour is dogshit.

Stylelint's playground is nice for some toying around. Still tweaking code and error messages.

Removed all twitter links from @projectwallace.com blog! Finally. Did a round previously removing them from all other places, but 8 years of blog took a bit more effort. Linking to people's personal sites now, cuz websites are cool

TIL `vertical-align` is a shorthand property 😲 developer.mozilla.org/en-US/docs/W...

Progress! Really enjoying this but also keep finding new issues, error messages to polish.

Stumbled across this issue while auditing a website earlier this week. Immediately made it a new rule for my upcoming stylelint-plugin. That thing is going to be *packed* with goodies.

Some people get mad when we shout at you for having to many declarations in one rule, but what if you'd just organize it in more layers? 😇 www.projectwallace.com/css-layers-v...

Trying to replace codecov with a @e18e.dev github action. Works pretty great and one less external dependency to install and configure and babysit. If only it would report bundle size *decreases* as well 😅 Will make an issue and maybe PR tomorrow

Does anyone have a good setup with Stylelint to lint an entire project instead of per-file analysis, or do I need to concat all the source/dist inputs myself and lint that? Seems a bit much.

The more I observe, the more I'm convinced that our youngest child is, in fact, Elmo

People are always looking for more actionable, opinionated feedback from Wallace. The sheer amount of raw numbers, tables and lists is complete, but overwhelming. I guess I'm writing a big stylelint plugin pack now.

Starting a new (well, old but never finished) project. This time it should be a lot easier to finish because I can just tell Claude what I want, give it clear specs and it should to it for me! Looking forward to shipping it and dogfooding wallace's css-parser and css-analyzer more!

🎉 format-css version 3 Created a small CLI script so you can format your CSS files from the terminal as well now. github.com/projectwalla...

Fun little task: improve the CSS code coverage. Did some code improvements on the github.com/projectwalla... repo and wanted to bump my coverage from 93.6% a little higher. Added some more tests and now we're at 94.6%. Mostly print styles not covered. github.com/projectwalla...

Please give this issue an upvote if you can spare a minute. It would make my life easier to calculate your CSS coverage. ✌️ issues.chromium.org/issues/40101...

Finally mustered up the energy to make a repro for Playwright for its strange CSS coverage issues: github.com/microsoft/pl... Blogged back in October www.projectwallace.com/blog/better-...

Almost done with updating all @projectwallace.com packages with my new stack for shipping libraries: - write source in TS - tsdown for bundling and generating dts - publint (integrated in tsdown) - oxlint - oxfmt - vitest - dependabot - codecov, also for bundle analysis

Another life goal: ✅ This was good fun! @bkardell.com and @meyerweb.com were really cool about this and had some really good questions that made me rethink some aspects of Wallace. 10/10 would recommend. 20 year old me still can't believe I get to make stuff like this.

New Igalia Chats episode 🎙️ We sat down with @veneman.dev of @projectwallace.com to dig into the study of CSS on the Web — how it's analyzed, what the data reveals, and why it matters. 🎧 Give it a listen: www.igalia.com/chats/projec...

Tried some wildly different fonts but I think Teko is just the best reflection of my border-radius:0 design. Added 2 gradients to the header at a late stage, quite like them. Added a lot more spacing to the homepage, but made the forms to submit URL a bunch smaller.

Writing specificity with commas as separators is confusing, as @meyerweb.com noted. The CSS Selection highlighted this with some edge cases like 146,546,159 which could be read as 1 number, depending on your thousands separator, which depends on locale. A very good point. What should use instead?

I'm considering hiring a designer for a couple of hours to help me with some things on @projectwallace.com. Homepage needs work and the other pages lack coherence. Do you have recommendations for a designer or how to approach this?

Can't wait to give grid-lanes a spin to see if I can reduce the amount of wasted space in our CSS analysis page.

And the video is live. It's a long one, but I made sure to time stamp it if you just want to jump to the results for each section (but you should totally just watch the entire thing 😅) youtu.be/PBDU2krty0M