---
title: "Jam | Console logs, network requests, and more"
image: "https://cdn-jam-screenshots.jam.dev/6f24fdcb6b7d1620cd0ef9027ef71d1f/screenshot/5686fa89-37dc-4e5d-8b14-ec97d54a7fc4.png"
url: "https://jam.dev/c/284e6350-e653-415e-baa3-09384027850c"
capturedOn: "http://localhost:3000/"
type: "screenshot"
browser: "Chrome 129.0.6668.100"
os: "Windows (x86) 11"
screen: "1217x1204"
country: "ES"
timezone: "Europe/Amsterdam"
author: "Chantal van Nuland"
date: "2024-10-16T09:14:53.467Z"
---

Unhandled Runtime Error
Error: [Link resolver error] Unknown type
Declared type: page
Expected one of:
- author
- event
- article
- doc
- blog
- place
- product
[Link resolver error] Unknown type
Declared type: page
Expected one of:
- author
- event
- article
- doc
- blog
- place
- product

Source
src\components\Header.tsx (8:20) @ async Header

   6 | export default async function Header({ lang }: { lang: string }) {
   7 |   const client = createClient();
>  8 |   const settings = await client.getSingle("settings", { lang });
     |                    ^
   9 |
  10 |   // Fetch the locales and languages
  11 |   const locales = await getLocales();

## Comments

**Chantal van Nuland** · 2024-10-16T09:14:53.467Z

Unhandled Runtime Error
Error: [Link resolver error] Unknown type
Declared type: page
Expected one of:
- author
- event
- article
- doc
- blog
- place
- product
[Link resolver error] Unknown type
Declared type: page
Expected one of:
- author
- event
- article
- doc
- blog
- place
- product

Source
src\components\Header.tsx (8:20) @ async Header

   6 | export default async function Header({ lang }: { lang: string }) {
   7 |   const client = createClient();
>  8 |   const settings = await client.getSingle("settings", { lang });
     |                    ^
   9 |
  10 |   // Fetch the locales and languages
  11 |   const locales = await getLocales();

## Not in this document

This is the summary tier. The captured events — console logs, network requests, user actions, and video frames — are not here: reading them needs filters, paging, and auth, so they live behind the Jam MCP server and CLI. Start at `getDetails`.

MCP: `https://mcp.jam.dev/mcp` (setup: https://jam.dev/docs/jam-mcp). CLI: `curl -fsSL https://native.jam.dev/install | bash` (https://jam.dev/docs/cli).