building on the foundations of the core architecture, the experimental integration for @astrodotbuild is ready
so now you can have a tool panel and SSR for lit with one integration definition ๐
#WebComponents#Vite#Frontend#Astro
using @HyperFrames_ for the vite plugin for lit (https://t.co/jsZ3QaiPR7) was kinda nice since i already outlined the main features and the underlying design system
@RyanCarniato while i recently found snake_case easier to parse with my eyes, i think it would be considered a crime in JS land
that beeing said, having it as close to โstandardโ as sensible would be great
@albertoblaz just tried something because i need a somewhat large sprite
it seems chromium does not do double requests anymore
safari does 3 requests while FF does 2
using caches - FF seems to consolidate the requests (not always), but safari only caches the prefetch
@kossnocorp i would recommend giving @tothemoonrepo a try
it's nice that you can have multiple languages/frameworks/runtimes in one schema ๐คนโโ๏ธ
@mattpocockuk how do would feel about dual - with one being square-ish like the LG DualUp?
i imagine it so weird that it may be nice
(horses for courses i guess ๐ )
https://t.co/027qZC7Tiz
@batzdev @FredKSchott@ThePrimeagen@elysiaJS i guess it's: bring your own typesafety system
even https://t.co/muXDB25OsB could be nice
what would be even more interesting is validationโฆ any hot takes?
"your scale depends on how well users write queries"
- @ThePrimeagen
for @FredKSchott it's a matter of how many users will spam astro projects with magnificent art ๐
@adamwathan i'm usually for custom props, but i don't see myself tinkering with a sizing system like .w-* that you can redefine
i would see the use in doing something like this though:
.var-space { --var-space: 2rem }
.parent { gap: var(--var-space) }
.child { gap: var(--var-space) 1rem }
@adamwathan awww yisss, at first glance these got me excited (besides @lightningcss)
was always wondering about why layers declarations won't end up in real layers ๐