projectwallace.com
CSS analyzers that check your complexity, specificity, performance, Design Tokens, custom properties and much more. By @veneman.dev
46 posts
72 followers
69 following
Prolific Poster
Active Commenter
comment in response to
post
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.
comment in response to
post
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.
comment in response to
post
🚢🚢🚢
All these new UintArrays keep me on my toes
comment in response to
post
Using it to display the unique colors found in CSS. Using column layout allows for nice visual grouping of the colors that's harder to do with grid or flex.
www.projectwallace.com/design-token...
comment in response to
post
Yup, sounds like a job for github.com/projectwalla... which also powers projectwallace.com/design-tokens.
comment in response to
post
Huge shoutout to Huntabyte for recording this video that sparked the idea and influenced the implementation *big time*
www.youtube.com/watch?v=e1vl...
comment in response to
post
And you can also resize the width of the table/code view. This makes the page more like an actual editor.
comment in response to
post
Created an issue so I don't forget github.com/projectwalla...
comment in response to
post
Sounds like an excellent tool to have. Have run into this *a lot* as well so I'm tempted to implement something for this.
comment in response to
post
I've been working on a StyleLint plugin package a while back, this would be an excellent use case. Evaluating is tricky so we'd have to restrict testing against non-calc() values. Sounds like a doable thing.
comment in response to
post
Also very disappointed in my typing skills.
comment in response to
post
Another one: if you were writing very old-skool CSS with some insane browserhack like `!ie` instead of `!important` we would actually still print !important.
Now you can have your `!ie`.
But I'm bvery disappointed if you actually do.
github.com/projectwalla...
comment in response to
post
This is *very* nice
comment in response to
post
position for chief marketing officer is still open, sir
comment in response to
post
They actually can, most of the uncovered CSS is because I didn'tclick enough of the UI that these parts got covered. It's more of an indication that Wallace's UI is broad and complex than that it's Tailwind's or Svelte's fault 😅
comment in response to
post
Even then it's helpful! The example shows coverage testing for projectwallace.com itself which uses both Tailwind and Svelte styling. There's some gaps in my ability to fully cover all website scenarios, but still there's also some CSS that I found that shouldn't be there at all.
comment in response to
post
Some highlights of the features:
🔸 Prettifies all CSS, even if it's part of a `<style>` element inside HTML
🔹 Inspect coverage per origin
🔸 Show which lines are not covered according to the report
🔹 The first page where there's a "load an example" button because these JSON's aren't easy to generate
comment in response to
post
Another fix: `::highlight(MyCustomName)` would not render the custom name, but now it does! github.com/projectwalla...
comment in response to
post
🥳
comment in response to
post
Search results now get an outline around the matched part, this makes it easier to spot why a certain property ends up in the search results 🥳