github.com/DanielSant0s...

process is basically deno bundle to get a .js file then use with AthenaEnv to run on ps2

it definitely feels like they went form over function. i can't say there are too many screens where i went "this looks good" as opposed to "this is a total mess of legibility and distraction"

you can sort-of deal with this one by long pressing and releasing over the All Tabs buuut yeah it still sucks.

shot in the dark as this piqued my curiosity - perhaps they're using a browser that doesn't support OKLCH colors? (I've actually never heard of OKLCH but seems browser compat is only since ~2022/2023) developer.mozilla.org/en-US/docs/W...

Saw the comment; it is frustrating that open source projects can be perceived as abandoned as opposed to complete. It's one of the reasons why I now refrain from open sourcing things (lest it be thrown around as something terrible). Good on you for providing what seems like a nice QoL update!

FWIW I thought your answers on the latest @typescript.fm were all succinct and clear! Not sure if you felt this way after that one but IMO don't sweat it. Good episode!

I haven't but I'll check it out! Any video in particular you recommend?

I was able to use styleTransforms to achieve this like enhance.dev does though enhance.dev/docs/enhance...

I took a peak at the enhance-ssr source and didn't see any spot to handle this, so I figure this is intentional, but I think it would be nice to have!

The main hiccup I had was that I thought enhance-ssr scoped styles but, at least with enhance-ssr-deno, it didn't seem to. It's not explicitly mentioned as a feature in the README but scope="global" is used in the examples.

github.com/enhance-dev/...

My overall goal was to avoid HTML abstraction wherever possible. Enhance WASM seems to have the best balance by using vanilla html/js/css syntax. I still wish I didn't need it, but the nature of SSR is writing browser code while not on a browser, so it is understandable that you need *something*

As for SSR that's been a whole separate challenge. I've tried

- enhance.dev (via enhance WASM on Deno)
- Lit
- Rendering into happy-dom (jakelazaroff.com/words/isomor...)
- My own implementation of enhance but leveraging declarative shadow dom for slots/encapsulation

TLDR; just use enhance

What actually sucks though is the shadow DOM. At this point I am not sure they should be used if you're not distributing web components to unknown environments. If you just want slots / style encapsulation for a typical component workflow it brings on too much friction.

nice tail