and thank you to all that submitted! you didn't make it easy to pick our nominees, and we appreciate all of you!

we're hoping to get a list of honorable mentions, apps on the horizon, shout-outs, and apps that also stole our hearts compiled by the end of the awards ❤️‍🔥

clearly they must be struggling to follow the recipes

i mean, currently Metro doesn't have tree shaking. From Expo's perspective, our goal is to start stabilising it as a feature but we'd make it export-all aware. From the standpoint of circular imports, live bindings make this mostly safe. But there can still be gotchas

fixed-ish~~
github.com/tadfisher/an...
tangled.org/@kitten.sh/s...

oh on web.... i'm not sure imagemanipulator is in great shape if implemented at all on web lol
we're not yet very consistent about that. i have high hopes in mediabunny for media shenanigans on web though

imagemanipulstor ? compress corresponds to the quality output and is specified via saveAsync. can fwd and see if anyone knows more though if it's giving you grief

hm does blocking the dev of the app block the app though? not that it matters much since they can just create more accounts & apps, but basically just seeing an app and a big install button first feels bad here 😅

the worst part imo is that it started as regular user accounts. But based on my notifications and this^ it's now github app bot accounts, which can't even be blocked

obv spam is happening via either of these, but spam from a source that can't even be blocked feels even worse

but yea, the amount of JS features (and CSS properties) that even require prefixing/transpilation/polyfills is so small that personally I don't see the point of it over a lint rule. I'm hoping we can just remove this eventually
Actually, maybe we should just be picking a good default for now

oh fwiw we only apply browserlist to CSS in Expo 😅 it'd be used if you were to slot in preset-env manually i guess (don't know if it supports browserlist) but it's otherwise only fed into lightningcss afaik

I do wonder whether the CSS baseline makes most of it obsolete, yea. I feel the same way about JS library transpilation fwiw, and the main blocker here is the lack(?) of a linter that just points out what's not supported in a configurable range

there's still kind of a place for a small SC lib with ordering guarantees (at least if it wouldn't be used for SSG but mostly dynamic apps) and without withComponent/styled(X) imo and with more of a CSS var focus

I vaguely remember @joshwcomeau.com writing a lot about that balance and subset

oof now I'm also curious how much of the parsing can be cut out with CSS nesting and if it's supported by the StyleSheet API

ah the project & history that went on a little too long 😂😛 yea I'm assuming that comment refers to this bug. fwiw as far as I know it didn't affect Firefox or Safari Webkit if I recall correctly though

spinning up multiple transform workers 😅 I'm not a fan of the warning being in the bundler itself so may look to disabling and moving it to our startup & install checks instead, where it belongs 😄

"make it work machine wheel people" 😫

please :c, or else >:c