Back to catalog / Developer tools
Expo DOM Components for Incremental Migration
Run existing web components in a native app’s WebView while preserving their web rendering.
Skills
Use when an Expo app needs charts, rich-text editors, or other DOM-dependent web libraries. Put the `"use dom"` directive at the top of a standalone component file, keep one default export, pass only serializable props, and include CSS in that file. Do not use DOM components in `_layout` or for simple UI and performance-critical native paths; weigh WebView overhead and migrate incrementally.
Permissions
Prerequisites
- An Expo project with a web component or DOM library and a compatible Expo `expo/dom` package.
Permissions
- Adds a WebView to the UI path and can pass data across the DOM boundary; do not pass secrets or non-serializable objects as props.
Limitations
WebViews add overhead and limit deep native integration; verify behavior on real iOS and Android builds.
Pinned upstream source
- Repository
- openai/plugins
- File path
- plugins/expo/skills/use-dom/SKILL.md
- Pinned commit
0722921d5542fc593105c27bd52630babd8b8c2a- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: MIT
Compatible tools
Codex · Expo DOM
Main topic
Take a coding Agent change from context to verification