I'm getting close to replicating my website in Lume. Overall I like it and some things were actually easier to do than in Astro. What I dislike is the inconsistency of the typings. Both layouts and components receive Lume.Data, but some are missing in components such as the current URL and data defined via _data.* files. Lume provides no types to distinguish these cases so it looks like I'm going to have to do it myself.
Current events show us more than ever social media's biggest problem: that's it's always everything all the time, with no breaks at all. That can't be good for people's mental health.
With my custom Lume plugins, I'm getting really close to the Astro experience now. - My JSX plugin gives me slots and class:list. - My icon plugin creates a single SVG spritesheet instead of adding one file per icon. - My picture plugin downloads remote images if they're from a whitelisted domain.
Not quite using <slot>, but instead you can add a prop slot to immediate children and the component can access them via props.slots.get("whatever"). Dead simple to implement
I found a bug on GitHub. Open any repository and use the search function. Open any issue from the search results. Go to the repository overview by clicking the repository name on the top of the page next to the GitHub logo. The title bar with the star button, fork button etc is gone.
Pretty ironic how a person who criticized me many years ago for using FurAffinity over any of the smaller alternatives is now still very active on Twitter and probably Discord (can't verify that apart from the existence of a profile link) and other profiles seem dead.
Still testing Lume as an alternative to Astro. The latter is nice to use, but it feels like it's too much for my website. I don't use a lot of its capabilities. With Lume there's ironically less type safety despite using Deno instead of Node. That's because for hot reloading it needs you to use weird constructs instead of regular imports. What is way easier with it, though, is writing plugins. I replaced the built-in JSX one with a custom one adding a "class:list" attribute that works like Astro's. Now I'm replacing the built-in icons plugin with my own one which generates an SVG sprite sheet instead of individual SVG files. For better or worse, you have more control over things.
@swiftyshq I really can't stand the screen being slightly wobbly right in the middle. You can see it because the brightness is slightly different, and you can feel it with your finger. No thanks.