feat: blog

[whitep4nth3r]

Merge this on 3rd March.

Things to do

Missing a11y tests for 6 component(s):

• AuthorAvatar.vue
• AuthorList.vue
• BlogPostListCard.vue
• BlogPostWrapper.vue
• BlueskyComment.vue
• BlueskyComments.vue

To do before merging

• delete test posts!

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
npmx.dev	Ready	Preview, Comment	Feb 11, 2026 1:00pm
npmx.dev-vercel	Ready	Preview, Comment	Feb 11, 2026 1:00pm

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
docs.npmx.dev	Ignored	Preview	Feb 11, 2026 1:00pm
npmx-lunaria	Ignored		Feb 11, 2026 1:00pm

[github-actions]

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File	Note
lunaria/files/en-GB.json	Localization changed, will be marked as complete. 🔄️
lunaria/files/en-US.json	Source changed, localizations will be marked as outdated.
lunaria/files/fr-FR.json	Localization changed, will be marked as complete. 🔄️

Warnings reference

Icon	Description
🔄️	The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (3)

server/api/atproto/bluesky-oembed.get.ts (2)

24-24: Consider defensive handling for regex match despite schema validation.

The non-null assertion and type cast rely on the schema having validated the URL format beforehand. Whilst this is mathematically sound per the comment, the coding guidelines recommend always checking array access by index. A defensive approach would guard against future refactoring that might break this assumption.

🛡️ Optional defensive approach

-      const [, handle, postId] = url.match(BLUESKY_URL_EXTRACT_REGEX)! as [string, string, string]
+      const match = url.match(BLUESKY_URL_EXTRACT_REGEX)
+      if (!match || !match[1] || !match[2]) {
+        throw createError({ statusCode: 400, message: ERROR_BLUESKY_URL_FAILED })
+      }
+      const [, handle, postId] = match

As per coding guidelines: "ensure you always check when accessing an array value by index".

---

27-32: Consider adding a timeout for the external API call.

The $fetch call to Bluesky's public API could hang if their service is slow or unresponsive. Adding an explicit timeout would improve resilience.

⏱️ Optional timeout configuration

       const { did } = await $fetch<{ did: string }>(
         `${BLUESKY_API}com.atproto.identity.resolveHandle`,
         {
           query: { handle },
+          timeout: 5000,
         },
       )

nuxt.config.ts (1)

93-108: Confirm a one‑year cache is acceptable for registry endpoints.
isr: true plus cache.maxAge of one year could serve stale docs/provenance/files if upstream data changes. If freshness matters, consider a shorter TTL or an explicit isr expiration.

[whitep4nth3r]

@jonathanyeong just merged main into this branch, another nightmare

the author avatars are no longer showing on the blog article now and I cannot work out why 😓