expo-observe

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

EAS Observe

EAS Observe

EAS Observe tracks startup, navigation, and custom-event performance from production Expo apps.
Source of truth: https://docs.expo.dev/eas/observe/ — always consult the canonical docs when API details matter, especially get-started, configuration, integrations, and the metrics reference. EAS Observe is evolving; this skill's references are written to stay accurate but may lag the docs.
EAS Observe 用于追踪生产环境中Expo应用的启动、导航及自定义事件性能。
权威来源: https://docs.expo.dev/eas/observe/ — 当涉及API细节时,请务必参考官方文档,尤其是入门指南、配置、集成以及指标参考部分。EAS Observe 处于持续演进中,本技能的参考内容会尽量保持准确,但可能会滞后于官方文档。

Which reference to read

参考文档选择

The three reference files in
./references/
cover the three things people typically need this skill for:
  • Adding EAS Observe to a project
    ./references/setup.md
    . Install, wrap the root layout (
    AppMetricsRoot
    on SDK 55,
    ObserveRoot
    on SDK 56+), call
    markInteractive()
    (global on SDK 55, via the
    useObserve()
    hook on SDK 56+), and optional per-route navigation metrics through the Expo Router / React Navigation integrations.
  • Querying metrics from the terminal
    ./references/queries.md
    . The five
    eas observe:*
    commands —
    metrics-summary
    ,
    metrics
    ,
    routes
    ,
    events
    ,
    versions
    — with flags, table layouts, JSON shapes, and common workflows.
  • Reading a dashboard or CLI output
    ./references/metrics.md
    . Target thresholds per metric, what the TTI
    frameRate.*
    params mean, and diagnostic patterns for telling slow-but-smooth startup apart from main-thread contention or hard blocks.
./references/
目录下的三份参考文件分别对应人们使用该技能的三类典型需求:
  • 在项目中添加EAS Observe
    ./references/setup.md
    。包括安装、包裹根布局(SDK 55版本使用
    AppMetricsRoot
    ,SDK 56+版本使用
    ObserveRoot
    )、调用
    markInteractive()
    方法(SDK 55版本为全局方法,SDK 56+版本通过
    useObserve()
    钩子调用),以及可选的、通过Expo Router / React Navigation集成实现的路由级导航指标。
  • 通过终端查询指标
    ./references/queries.md
    。涵盖五个
    eas observe:*
    命令——
    metrics-summary
    metrics
    routes
    events
    versions
    ,包括命令参数、表格布局、JSON结构及常见工作流程。
  • 解读仪表盘或CLI输出
    ./references/metrics.md
    。包括各指标的目标阈值、TTI
    frameRate.*
    参数的含义,以及区分“缓慢但流畅的启动”与“主线程阻塞”或“硬卡顿”的诊断模式。

Quick links to the docs

官方文档快速链接