Recent searches
Search options
I thought this post on Twitter about the #CoreWebVitals of the homepages of #javascript tools and frameworks was interesting, and I thought I’d cross post it here
It uses this tool: https://page-speed.dev/
Here’s how some of my favorite tools do: @eleventy, @astro, @deno_land Fresh, #Qwik
Original post: https://x.com/fredkschott/status/1756407637087010947?s=61&t=9qVqQJY7E1ikFhtau9dXug
@hasanhaja take a look at https://treo.sh/sitespeed/ for some possibly unexpected data. Local testing and simulation is not that realistic, apparently.
@hasanhaja I’ve recently come across a really interesting ssg called Capri - https://capri.build/. It’s uses Vite and the usual js frameworks to build an ssg with islands similar to Astro but without forcing you into .astro components.
@rusticola Thanks for sharing, I’ve not heard of this before 
The file-extension based “islands” feels similar to how it works in Fresh.
A claim I don’t agree with is that the server components need to be written as Astro components. You only need to assemble your page in a root Astro component. Otherwise, you can write all of your components in any framework and use the client directives to mark islands. This gets you the same benefits in the output.
Nevertheless, it looks really cool!
Curious to find out how lagoons work syntactically. You can achieve the same effect by passing Astro components (or unhydrated framework components) as children to islands, but sometimes it gets a little confusing to interlace them too much
@hasanhaja it’s just a *.lagoon.* file extension - https://capri.build/docs/project-structure/islands/