# DevLogger — Expo example (Expo Go, SDK 54)

A minimal **managed Expo** app that consumes the local `@zearaez/devtool`
workspace. It runs in **Expo Go** with no native build, proving the package is
Expo-compatible. Copy-to-clipboard works via `expo-clipboard` (bundled in Expo
Go), which DevLogger auto-detects.

## Run it in Expo Go

From the **repo root** (first run builds the library so the example can import it):

```sh
yarn install
yarn prepare          # build @zearaez/devtool into lib/
yarn example-expo start
```

Then press `i` / `a`, or scan the QR code with the **Expo Go** app (SDK 54) on
your phone. Fire a few requests, then tap the floating bubble to open the panel.

> Because the example imports the **built** package (`lib/`), re-run
> `yarn prepare` after editing files in `src/`. (Or run `yarn prepare` in watch
> terms by rebuilding when you change the library.)

## Notes

- **`expo-doctor` warnings are expected here** and safe to ignore:
  - *Metro config override* — `disableHierarchicalLookup` is intentional (see
    [metro.config.js](metro.config.js)); it forces react/react-native to resolve
    from this app rather than the library's own newer dev copies at the repo root.
  - *Duplicate react / react-native* — the repo root pins newer versions for
    building/testing the library; this app pins the SDK 54 versions. They're
    isolated by `nmHoistingLimits: workspaces` and only the app's JS bundle runs
    in Expo Go.
- No `android/` or `ios/` folders: this is the managed workflow. Run
  `npx expo prebuild` only if you want a native/dev-client build.