Blyp Client and Expo
Install blyp-client-expo after blyp-core when the application needs Blyp outside the server runtime. This preset covers both @blyp/core/client for browsers and @blyp/core/expo for Expo apps, including remote sync, retry queues, and connector forwarding requests through Blyp ingestion.
When to install it
- the repo logs from browsers with
createClientLogger() - the repo logs from Expo with
createExpoLogger() - client-side logs should be mirrored to Blyp ingestion or forwarded into configured connectors
What it covers
- default browser ingestion path at
/inngest - retry queue behavior for browser and Expo delivery
- absolute endpoint requirement for Expo
expo-networkrequirement for Expo remote sync- client connector requests for PostHog, Sentry, and named OTLP targets
Download raw skill file
Use the canonical source file directly if you want to copy it into an agent skill directory without copying from the rendered page.
/skills/blyp-client-expo/SKILL.md| Agent | Project-local path | Global path |
|---|---|---|
| Codex | .agents/skills/blyp-client-expo/SKILL.md | ~/.agents/skills/blyp-client-expo/SKILL.md |
| OpenCode | .opencode/skills/blyp-client-expo/SKILL.md | ~/.config/opencode/skills/blyp-client-expo/SKILL.md |
| Claude Code | .claude/skills/blyp-client-expo/SKILL.md | ~/.claude/skills/blyp-client-expo/SKILL.md |
Related docs
Canonical skill source
Copy the exact markdown file contents and drop them into your agent skill directory.
---
name: blyp-client-expo
description: Portable Blyp add-on skill for browser and Expo logging with @blyp/core/client, @blyp/core/expo, default /inngest ingestion, retry queues, and connector forwarding requests through Blyp.
---
# Blyp Client and Expo
## What this skill is for
Use this add-on when Blyp should emit logs from browsers or Expo apps into a Blyp-enabled backend.
## When to use it
- Adding `createClientLogger()` in a browser app
- Adding `createExpoLogger()` in an Expo app
- Enabling remote sync to Blyp ingestion
- Requesting PostHog, Sentry, or OTLP forwarding from the client side
## Blyp-specific rules and constraints
- Install `blyp-core` first.
- Browser apps import from `@blyp/core/client`.
- Expo apps import from `@blyp/core/expo`.
- Browser ingestion defaults to `/inngest`.
- Browser delivery retries retryable failures with an in-memory queue.
- Expo requires an absolute `http://` or `https://` ingestion endpoint.
- Expo requires `expo-network` for connectivity-aware retry behavior.
- Browser and Expo connector requests still go through Blyp ingestion first.
## Required implementation steps
1. Pick the correct runtime import:
- Browser: `createClientLogger` from `@blyp/core/client`
- Expo: `createExpoLogger` from `@blyp/core/expo`
2. Keep the endpoint aligned with the server ingestion route:
- Browser default: `/inngest`
- Expo: absolute backend URL such as `https://api.example.com/inngest`
3. Configure delivery options only when the repo needs custom retry behavior.
4. If connector forwarding is requested, set `connector` on the client logger and verify the server connector exists.
5. For Expo, ensure `expo-network` is installed before relying on remote sync.
## Verification checklist
- Browser code imports `@blyp/core/client`
- Expo code imports `@blyp/core/expo`
- Browser endpoint defaults to or matches `/inngest`
- Expo endpoint is absolute
- `expo-network` is installed when Expo remote sync is enabled
- Any connector request is backed by a server-side Blyp connector
## References
- Browser import path: `@blyp/core/client`
- Expo import path: `@blyp/core/expo`
- Main APIs: `createClientLogger()`, `createExpoLogger()`
- Connector request shapes: `"posthog"`, `"sentry"`, `{ type: "otlp", name: "<target>" }`