chore(computer-vision): upgrade vision-camera to 5.0.6 and refresh doc links

[NorbertKlockiewicz]

Description

Upgrades react-native-vision-camera in the computer-vision example app from 5.0.0-beta.7 to ^5.0.4, adds the now-required react-native-vision-camera-worklets companion package (needed for Frame Processors / useFrameOutput in v5 stable), and updates VisionCamera documentation links in the docs site to point to the new official location at https://visioncamera.margelo.com (previously the temporary react-native-vision-camera-v5-docs.vercel.app preview domain).

Introduces a breaking change?

• Yes
• No

Type of change

• Bug fix (change which fixes an issue)
• New feature (change which adds functionality)
• Documentation update (improves or adds clarity to existing documentation)
• Other (chores, tests, code style improvements etc.)

Tested on

• iOS
• Android

Testing instructions

1. yarn install at the repo root.
2. cd apps/computer-vision && yarn ios (pods will reinstall for the new native module).
3. Open the VisionCamera screen and verify each task (Classification, Object Detection, OCR, etc.) streams frames and renders results without the Cannot use Frame Processors - react-native-vision-camera-worklets is not installed! error.
4. Build the docs site (cd docs && yarn start) and confirm the VisionCamera Integration page links resolve to the new visioncamera.margelo.com URLs.

Screenshots

N/A

Related issues

None

Checklist

• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have updated the documentation accordingly
• My changes generate no new warnings

Additional notes

• Doc URL change applies to both the current docs and the version-0.8.x versioned copy.
• Version ^5.0.4 matches the latest published stable release; react-native-vision-camera-worklets is pinned to the same major/minor to stay in sync.
• The ios app doesn't build because of the bug in vision camera source code

[msluszniak]

Hmm, why is lint failing here?

[msluszniak]

Pushed a workaround commit (a3d3da5) to unblock CI on this PR.

The lint failure here was not caused by your changes — it was triggered by them. react-native-vision-camera@5.0.4 ships a postinstall: "tsc || exit 0;" script. On CI Linux runners (where tsc happens to be on PATH inside the postinstall scope), the script invokes tsc with no args, which walks up to find the monorepo root tsconfig.json (no outDir set), and emits compiled .js files next to every .ts source across the repo. The || exit 0 swallows the error so install "succeeds", then yarn lint (with its **/*.{js,ts,tsx} glob) trips on the stray files.

It only manifested here because this PR is the first to bump vision-camera to 5.0.4, invalidating Yarn's per-version build state cache and triggering a fresh build. macOS hides the bomb because tsc isn't on PATH in that scope, so the || exit 0 silently no-ops.

The commit uses Yarn's dependenciesMeta.<pkg>.built: false to opt out of vision-camera's install scripts entirely — the package ships pre-built lib/ so the postinstall is redundant for consumers anyway.

We'll file an upstream issue against vision-camera (recommended fix: remove the postinstall entirely, or rename it to prepare so it doesn't run for npm-registry installs).

[msluszniak]

Followup: with the install-script bomb defused, the typecheck step now actually runs and surfaces several real API incompatibilities between vision-camera 5.0.0-beta.7 (previous) and 5.0.4 (this PR). The example screen at apps/computer-vision/app/vision_camera/index.tsx still references getCameraFormat, Templates, and a few <Camera> props (outputs, format, orientationSource) that 5.0.4 dropped.

Pushed 54d1c66 adding apps/computer-vision/vision-camera-shims.d.ts — a .d.ts augmentation that re-declares the missing exports with permissive types so tsc --noEmit passes. Runtime behavior of that screen is broken regardless — the shim just unblocks unrelated PRs from being held up by the typecheck failure.

The real fix is migrating the vision_camera screen to vision-camera 5.x's new hook-based API (useCamera, useFrameOutput, etc.). That's a separate, larger piece of work; a TODO is documented in the shim file. CI should now be green on this PR.

[msluszniak]

Followup: pushed 9f8f42a migrating the screen to vision-camera 5.x's API and removing the type shim file.

Turns out the migration was much smaller than the shim's TODO suggested. The only 5.x breaking changes affecting our code were:

• getCameraFormat (removed)
• Templates (removed)
• <Camera format={...}> prop (removed)

All of these were used in a single useMemo block that selected Templates.FrameProcessing and forwarded it to <Camera>. In 5.x that's achieved implicitly by useFrameOutput's defaults (HD_16_9 resolution, 'native' pixel format), so the explicit format selection is no longer needed.

Everything else the screen and task files used (Camera, useCameraDevices, useCameraPermission, useFrameOutput, Frame, <Camera> props outputs/isActive/device/orientationSource="device") is unchanged in 5.x.

Net diff: −13 lines from vision_camera/index.tsx + −26 lines from the now-deleted shim. Three commits on this PR:

1. a3d3da5 — disable vision-camera install scripts via dependenciesMeta (workaround for upstream postinstall bug, removable when mrousavy/react-native-vision-camera#3764 ships in a release)
2. 54d1c66 — type shim (now superseded)
3. 9f8f42a — actual migration + shim removal

CI green on all three steps.