fix: use typed ATproto client when fetching bsky embeds

The oembed endpoint used a raw fetch and is missing the `/xrpc` path prefix. This causes
a 502 error when trying to fetch embeds. We can use the typed client to be consistent
with author-profiles and other atproto api routes. And means we don't need to specify the
/xrpc path in the fetch.

Author: jonathanyeong

lexicons.json

@@ -10,6 +10,7 @@
     "app.bsky.feed.getPostThread",
     "app.bsky.feed.getPosts",
     "app.bsky.feed.post",
+    "com.atproto.identity.resolveHandle",
     "com.bad-example.identity.resolveMiniDoc",
     "site.standard.document"
   ],
@@ -98,6 +99,10 @@
       "uri": "at://did:plc:4v4y5r3lwsbtmsxhile2ljac/com.atproto.lexicon.schema/app.bsky.richtext.facet",
       "cid": "bafyreidg56eo7zynf6ihz4xb627vwoqf5idnevkmwp7sxc4tijg6xngbu4"
     },
+    "com.atproto.identity.resolveHandle": {
+      "uri": "at://did:plc:6msi3pj7krzih5qxqtryxlzw/com.atproto.lexicon.schema/com.atproto.identity.resolveHandle",
+      "cid": "bafyreigckmqtt3jrtzd7tvigjatnz6ajqyafs26h5pwcudwag2anedxnmu"
+    },
     "com.atproto.label.defs": {
       "uri": "at://did:plc:6msi3pj7krzih5qxqtryxlzw/com.atproto.lexicon.schema/com.atproto.label.defs",
       "cid": "bafyreig4hmnb2xkecyg4aaqfhr2rrcxxb3gsr4xks4rqb7rscrycalbrji"

lexicons/com/atproto/identity/resolveHandle.json

@@ -0,0 +1,41 @@
+{
+  "id": "com.atproto.identity.resolveHandle",
+  "defs": {
+    "main": {
+      "type": "query",
+      "errors": [
+        {
+          "name": "HandleNotFound",
+          "description": "The resolution process confirmed that the handle does not resolve to any DID."
+        }
+      ],
+      "output": {
+        "schema": {
+          "type": "object",
+          "required": ["did"],
+          "properties": {
+            "did": {
+              "type": "string",
+              "format": "did"
+            }
+          }
+        },
+        "encoding": "application/json"
+      },
+      "parameters": {
+        "type": "params",
+        "required": ["handle"],
+        "properties": {
+          "handle": {
+            "type": "string",
+            "format": "handle",
+            "description": "The handle to resolve."
+          }
+        }
+      },
+      "description": "Resolves an atproto handle (hostname) to a DID. Does not necessarily bi-directionally verify against the the DID document."
+    }
+  },
+  "$type": "com.atproto.lexicon.schema",
+  "lexicon": 1
+}

server/api/atproto/bluesky-oembed.get.ts

@@ -8,6 +8,8 @@ import {
   BLUESKY_URL_EXTRACT_REGEX,
 } from '#shared/utils/constants'
 import { type BlueskyOEmbedResponse, BlueskyOEmbedRequestSchema } from '#shared/schemas/atproto'
+import { Client } from '@atproto/lex'
+import * as com from '#shared/types/lexicons/com'
 
 export default defineCachedEventHandler(
   async (event): Promise<BlueskyOEmbedResponse> => {
@@ -21,15 +23,14 @@ export default defineCachedEventHandler(
        * If the schema passes, this regex is mathematically guaranteed to match and contain both capture groups.
        * Match returns ["profile/danielroe.dev/post/123", "danielroe.dev", "123"] — only want the two capture groups, the full match string is discarded.
        */
-      const [, handle, postId] = url.match(BLUESKY_URL_EXTRACT_REGEX)! as [string, string, string]
+      const [, handle, postId] = url.match(BLUESKY_URL_EXTRACT_REGEX)! as [
+        string,
+        `${string}.${string}`,
+        string,
+      ]
 
-      // INFO: Resolve handle to DID using Bluesky's public API
-      const { did } = await $fetch<{ did: string }>(
-        `${BLUESKY_API}com.atproto.identity.resolveHandle`,
-        {
-          query: { handle },
-        },
-      )
+      const client = new Client({ service: BLUESKY_API })
+      const { did } = await client.call(com.atproto.identity.resolveHandle, { handle })
 
       // INFO: Construct the embed URL with the DID
       const embedUrl = `${BLUESKY_EMBED_BASE_ROUTE}/embed/${did}/app.bsky.feed.post/${postId}?colorMode=${colorMode}`