yeskunall / www Goto Github PK

Why Markdoc?

Announcement post

Replace rehype-pretty-code with shikiji.

I say better, but really I mean something that will scale better than my current solution. As the amount of content grows, each dynamic image generated will slow down the Astro build.

I want to replace the dynamic generation of these images with something more static. That will speed up builds, and I think it will also be more maintainable.

Vercel does not recommend using vercel.json to rewrite URLs in Astro projects.

I can use edge middleware instead. I’m glad I came across the above warning in their docs before doing something stupid.

Looks like I’ll also be able to drop prefetch if I use swup/astro.

Vite v4.4 added support for Lightning CSS. Looks like Astro has already exposed some functionality, but there is no mention of it in their docs.

Opening this right now because I’m really interested in taking Lightning CSS for a test drive but haven’t had an excuse to so far.

Astro does a great job at bundling, but there are still room for improvements.

Ref: astro-compress, jampack, image-actions

TODO:

• Use a testing framework compatible with Astro (Vitest?)
• Write the first test (#7, #13)
• Setup GitHub CI/CD (Earthly?)

I usually use Supabase auth. But they’ve all been Next.js projects. So I will most likely run into some issues when setting it up with Astro.

I still want to use it, though. I really like how it integrates with PostgreSQL’s RLS. Also supports PKCE and social auth.

I have some custom response headers set in astro.config.ts which are not being applied in production ATM. They work using astro dev and astro preview.

I need to set them in vercel.json. That should fix it.