fix(nitro): print client ingest events to stdout

[evlogai]

Fixes #812 (Linear EVL-532).

Problem

The client ingest endpoint (_evlog/ingest.post.ts) accepts browser log events, runs the enrich hooks and sends the event to drains. It never writes the event to the console, unlike server events, which go through outputWideEvent. An app that has no drain configured therefore answers 204 to every client log and the event goes nowhere.

Fix

After enrichers have run, the route calls the existing outputWideEvent(wideEvent), then runs the drains as before. This is the same order emitWideEvent uses for server events, so the console carries the same event the drains receive. silent: true still suppresses the output, and pretty / stringify are honored.

Evidence

Regression test first: packages/evlog/test/nuxt/ingest-output.test.ts, run against the code before the fix:

FAIL  prints a client event to stdout when no drain is configured
AssertionError: expected "info" to be called 1 times, but got 0 times
FAIL  prints a client error to stdout through the error console method
AssertionError: expected "error" to be called 1 times, but got 0 times
FAIL  prints a client event and still runs the drain hook
AssertionError: expected "info" to be called 1 times, but got 0 times
Tests  3 failed | 1 passed (4)

After the fix:

ingest-output.test.ts + ingest-sampling.test.ts:  Tests 8 passed (8)
full packages/evlog suite:                        Test Files 101 passed (101), Tests 2046 passed (2046)
pnpm run lint:                                    exit 0
pnpm run typecheck:                               exit 0

The checks ran in the sandbox on this branch. The regression is a unit test that drives the route through h3 with useNitroApp mocked; I did not run it inside a live Nuxt app, so that end-to-end path is unverified.

Not in this PR

• No docs note or evlog doctor warning for apps without a drain. Those can follow if wanted.

ELI5

When a website sends a log to the server, the server accepted it but only forwarded it to a log service. If the app had no such service set up, the log was thrown away silently. Now the server also prints the log to its console, the same way it does for its own logs. Nothing else changes: the log still goes to the service when one is set up.

[vercel]

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

Project	Deployment	Actions	Updated
evi	Ready	Preview	Oct 10, 2026 10:10pm UTC
evlog-docs	Ready	Preview, v0	Oct 10, 2026 10:10pm UTC
evlog-render-lab	Ready	Preview	Oct 10, 2026 10:10pm UTC
evlog-telemetry	Building	Preview	Oct 10, 2026 10:10pm UTC
just-use-evlog	Ready	Preview	Oct 10, 2026 10:10pm UTC

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 287909fc-0955-4271-8dcb-a17495b2b49b

---

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Thank you for following the naming conventions! 🙏

[pkg-pr-new]

@evlog/cli

npm i https://pkg.pr.new/@evlog/cli@821

evlog

npm i https://pkg.pr.new/evlog@821

@evlog/nuxthub

npm i https://pkg.pr.new/@evlog/nuxthub@821

@evlog/signals

npm i https://pkg.pr.new/@evlog/signals@821

@evlog/telemetry

npm i https://pkg.pr.new/@evlog/telemetry@821

commit: 1810e6c