Project Wallace
@projectwallace.com
120 followers 70 following 60 posts
CSS analyzers that check your complexity, specificity, performance, Design Tokens, custom properties and much more. By @veneman.dev
Posts Media Videos Starter Packs
projectwallace.com
But the good news is: @netlify.com is now serving our website! 🥳
projectwallace.com
Looks like we're back. Keeping a close eye and hoping we'll stay online while we still need to finalize switching registrars.
projectwallace.com
We're experiencing some DNS issues while we're moving away from Vercel. Please hang on tight.

Fingers crossed that analyzing your CSS isn't the most important thing you were going to do today 🤞
projectwallace.com
Thinking of cooking up something to compare sets of CSS. Most likely for before/after sort of stuff, but perhaps other use cases too.

Visualisation of that will be tough, I guess. Rendering stats for a single site easily ends up with thousands of DOM nodes.

Would you use it?
projectwallace.com
Gave the ol' CMD+K menu a fresh lick of paint and added a search bar. Much more useful this way 😍
The old menu: 9 items, only some arbitrary pages. The new menu: all possible pages included grouped by type, as well as a new search field.
Reposted by Project Wallace
veneman.dev
Doing a very similar trick on the CSS Coverage inspector: create an array of start/stop elements to render an entire range instead of a single DOM node per line.

❌ DOM size before: 3145 nodes
✅ DOM size after: 686 nodes

(But gains depend on CSS size & patchiness of coverage of the selected file)
Browser showing the Wallace Coverage Inspector. One file is shown, with lines 1-14 covered and lines 15-18 uncovered. The devtools panel is open. The HTML inspector shows a single div to render the numbers 1 through 15. Another div is shown to render the numbers 15 through 18. Below the HTML inspector is a console panel that shows that `document.querySelectorAll('body *').length` evaluates to 686.
Reposted by Project Wallace
veneman.dev
I appreciate all 18 of you! +1 rank gained is still a plus in my book.
2025.stateofcss.com/en-US/other-...
State of CSS result table showing the "other tools" section. Project Wallace is listed near the bottom with 0.5% of respondents (18 people) indicating they use it. A tooltip says there's a +1 increase in rank.
Reposted by Project Wallace
projectwallace.com
🧛 Anyone up for counting the depth of your CSS nesting?
Could be interesting to spot deeply nested and hard to debug rulesets, declarations, etc.
Scatter plot and a table showing how deeply nested each seletcor, atrule, rule or declaration in a stylesheet is. This example has nesting declarations up to 6 levels deep.
Reposted by Project Wallace
veneman.dev
🆕 Spacing reset analysis

Sparked by @ohhelloana.blog's enthusiasm, this turned out to be a relatively simple feature! 🥳

A few gotchas:
- a gazillion ways to write 0 (scientific notation, floats, signed numbers)
- many spacing-related properties, potentially vendor prefixed (although unlikely)
Project Wallace analysis of CSS spacing resets. A table is shown with some CSS properties like margin, padding, margin-left, etc. The second table row is selected and down on the page is a devtools bar that shows all the related resets for the selected table row.
projectwallace.com
#CSSDay was a blast and the first act of applying quick wins was improving scrollbar styling after watching @nerdy.dev's talk.

Still recovering from the energy.
projectwallace.com
At #cssday where @miriam.codes is speaking truths
Miriam standing on stage before a slide that says "complexity is something to manage"
projectwallace.com
🆕 Container names.

Because we all sometimes forget to name a thing, or forget that we named it and never used it 😇
Project Wallace's CSS Analysis overview focusing on the atrules section, showing two panels about CSS containers. The first panel shows which container queries were found. The second panel shows which container names were found, both in container queries as well as declarations explicitly setting a `container-name` property (or via the `container` shorthand 🤮).
projectwallace.com
🆕 See which Media Features are used. Useful if you have many media queries and want a quick view of which features are queried.

Idea taken from @httparchive.org's CSS chapter.
Project Wallace's CSS analysis overview, focusing on the Atrules section. It shows several panels, the @media ones being relevant here. A panel on the left says `@media` with 2211 items (165 unique). The panel on the right says `media features` with 2679 items in total, 17 unique.
projectwallace.com
Published [email protected] and [email protected] to reduce their install size with ~50%.

css-analyzer shipped 2 versions of css-tree which is the only dependency but at a 'costly' ~2.03MB. It also ships CommonJS so we *could* even further get the number down.
projectwallace.com
The header needs some design tweaks with this additional item. I'm aware that alignment is a bit whack and the whole thing is cramped on small screens. Updates coming later this week.
projectwallace.com
The idea had been long on my issue list but this video from @syntax.fm convinced me to start it www.youtube.com/watch?v=F1s8...

Mine uses cookies + SSR instead of localStorage though.
Modern CSS Theming | Light Mode / Dark Mode and More!
YouTube video by Syntax
www.youtube.com
projectwallace.com
🔆 last night I shipped a light theme

There may be bits and bobs still not converted yet so please let me know if anything looks broken.

Also, grab some sunglasses 😎
Project Wallace's css analysis page but unlike every other screenshot posted here so far this one is white with black text.
projectwallace.com
🚢🚢🚢

All these new UintArrays keep me on my toes