evlog.dev valid

evlog

A modern TypeScript logger for everything you ship. Simple structured logs, wide events, and structured errors in one API - for scripts, libraries, jobs, edge, and requests.

For agents: evlog is a TypeScript logger offering structured logs, wide events and structured errors across Nuxt, Next.js, Hono and other frameworks, with docs and an MCP s

typescript loggerstructured loggingwide eventsevlogmcp server

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T12:26:26.038Z. Cached copy · Source on evlog.dev

# evlog

> A modern TypeScript logger for everything you ship. Simple structured logs, wide events, and structured errors in one API - for scripts, libraries, jobs, edge, and requests.

## Overview

- [evlog](https://www.evlog.dev/raw/index.md)

## Documentation Sets

- [evlog - full documentation](https://www.evlog.dev/llms-full.txt): Complete evlog documentation as structured markdown for deep retrieval.

## Developer resources

Machine-readable entry points for evlog.

- [evlog on GitHub](https://github.com/evloghq/evlog): Source code, issues, and releases.
- [evlog on npm](https://www.npmjs.com/package/evlog): The `evlog` package, plus `@evlog/cli`, `@evlog/nuxthub`, and `@evlog/telemetry`.
- [Docs MCP server](https://www.evlog.dev/raw/reference/mcp.md): Search and read this documentation from Cursor, Claude Code, or VS Code over streamable HTTP at https://www.evlog.dev/mcp.
- [Agent skills index](https://www.evlog.dev/.well-known/skills/index.json): Skills published by this site, following the /.well-known/skills convention.
- [Sitemap](https://www.evlog.dev/sitemap.xml): Every page of this documentation, with last modification dates.

## Get started

- [Install evlog](https://www.evlog.dev/raw/start/installation.md): Install evlog in your TypeScript project. Supports Nuxt, Next.js, SvelteKit, Hono, Express, Fastify, Elysia, NestJS, and standalone scripts.
- [Introduction](https://www.evlog.dev/raw/start/introduction.md): Understand what happened in your app with evlog: structured logging, wide events, and errors that explain what went wrong and how to fix it.
- [Quick Start](https://www.evlog.dev/raw/start/quick-start.md): Get up and running with evlog in minutes. Learn the log API, createLogger for wide events, useLogger for requests, and structured errors.
- [Choosing a TypeScript Logger](https://www.evlog.dev/raw/start/typescript-logging-library.md): Choose a TypeScript logging library around the way you debug. See where evlog fits, what to keep from your current setup, and how to try it.
- [Why start with evlog](https://www.evlog.dev/raw/start/why-evlog.md): The cheapest moment to add structured logging is before the first request. Pick evlog on day zero and the rest of the system inherits it.

## Learn

- [Catalogs](https://www.evlog.dev/raw/learn/catalogs.md): Scale typed error and audit catalogs from one file to a monorepo: conventions, an npm packaging recipe, and type augmentation.
- [Lifecycle](https://www.evlog.dev/raw/learn/lifecycle.md): An evlog event from creation to drain, across all three modes, through sampling, enrichment, and delivery.
- [Learn evlog](https://www.evlog.dev/raw/learn/overview.md): The mental model: three logging modes, the wide event lifecycle, sampling, typed fields, and redaction. Read it in order if you are new.
- [Auto-Redaction](https://www.evlog.dev/raw/learn/redaction.md): Automatically scrub PII from wide events before console output and drains. Built-in smart masking for credit cards, emails, IPs
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=evlog.dev · GET /v1/domain/evlog.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for evlog.dev:
1. POST https://agentwebmap.com/v1/sites/evlog.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://evlog.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/evlog.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/evlog.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.