[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-expo-expo-migrate-module":3,"mdc--hz5p1g-key":37,"related-repo-expo-expo-migrate-module":763,"related-org-expo-expo-migrate-module":871},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":26,"repoUrl":27,"updatedAt":28,"license":29,"forks":30,"topics":31,"repo":32,"sourceUrl":35,"mdContent":36},"expo-migrate-module","migrate Expo native modules to v2","Framework (OSS). Migrate an existing Apple\u002FSwift Expo native module from the Expo Modules API 1.0 definition DSL to the 2.0 macro API (sometimes called v2) while preserving its JavaScript and TypeScript contract. Use when converting or incrementally adopting @ExpoModule, @JS, @Event, @SharedObject, or @Record in an existing module. Do not use for creating a new module, general Expo SDK upgrades, or Android\u002FKotlin migrations.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"expo","Expo","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fexpo.png",[12,14,17,20,23],{"name":9,"slug":8,"type":13},"tag",{"name":15,"slug":16,"type":13},"TypeScript","typescript",{"name":18,"slug":19,"type":13},"Mobile","mobile",{"name":21,"slug":22,"type":13},"Swift","swift",{"name":24,"slug":25,"type":13},"Migration","migration",2190,"https:\u002F\u002Fgithub.com\u002Fexpo\u002Fskills","2026-07-24T05:36:31.183668","MIT",111,[],{"repoUrl":27,"stars":26,"forks":30,"topics":33,"description":34},[],"A collection of AI agent skills for working with Expo projects and Expo Application Services","https:\u002F\u002Fgithub.com\u002Fexpo\u002Fskills\u002Ftree\u002FHEAD\u002Fplugins\u002Fexpo-experiments\u002Fskills\u002Fexpo-migrate-module","---\nname: expo-migrate-module\ndescription: Framework (OSS). Migrate an existing Apple\u002FSwift Expo native module from the Expo Modules API 1.0 definition DSL to the 2.0 macro API (sometimes called v2) while preserving its JavaScript and TypeScript contract. Use when converting or incrementally adopting @ExpoModule, @JS, @Event, @SharedObject, or @Record in an existing module. Do not use for creating a new module, general Expo SDK upgrades, or Android\u002FKotlin migrations.\nversion: 1.0.0\nlicense: MIT\n---\n\n# Migrate an Expo Module\n\nMigrate the Swift side of an existing Expo module without changing its observable JS API. Treat the current JS\u002FTypeScript surface and tests as the compatibility contract. Leave Kotlin on the 1.0 DSL unless the user explicitly expands the task.\n\n## Prerequisite\n\nThe Expo Modules API 2.0 macros require `expo` `57.0.7` or newer. Before editing, check the target's installed version (`expo` in `package.json`\u002Flockfile, or `npm ls expo`). If it is older, stop and tell the user to upgrade first; do not attempt the migration against an unsupported version. This is a floor, not a guarantee: the exact macro and core surface still varies within `57.x`, so step 2 must still verify the checked-out source.\n\n## References\n\n- Read `references\u002Fmigration-map.md` before changing source. It contains the 1.0-to-2.0 mappings, semantic traps, and mixed-mode rules.\n- Read `references\u002Fexample.md` for a full before\u002Fafter walkthrough of one module through mixed mode to a complete migration. Consult it when you need to see how the per-member rules compose.\n- Read `references\u002Fcompatibility.md` when the checked-out `expo-modules-core` version or branch is not known to support every requested macro. It explains how to verify the actual compile-time and runtime surface instead of guessing from an SDK number.\n\n## Workflow\n\n### 1. Establish the contract\n\nInspect repository instructions and the worktree before editing. Locate the Swift module classes, records, shared objects, native views, JS\u002FTS bindings, tests, example app, podspec, and installed or checked-out `expo-modules-core`.\n\nInventory every exported item before rewriting it:\n\n- module and shared-object JS names\n- function names, arity, labels, defaults, nullability, sync\u002Fasync behavior, errors, and queue semantics\n- property names, mutability, and constant caching behavior\n- event wire names and payload shapes\n- record field names, defaults, requiredness, and nullability\n- shared-object constructors and instance\u002Fstatic placement\n- lifecycle hooks and views\n\nUse the TypeScript declarations and JS call sites to resolve ambiguity. Do not silently \"improve\" requiredness, rename an event, or change sync behavior during a syntax migration.\n\n### 2. Verify the available 2.0 surface\n\nInspect the macro declarations and matching core hooks in the dependency actually used by the target. Do not assume that all items in the 2.0 design are present because one macro compiles.\n\nClassify each 1.0 item as:\n\n- **Migrate:** both its macro and required core runtime support exist.\n- **Keep in DSL:** mixed mode preserves it safely, or 2.0 lacks an equivalent.\n- **Blocked:** migration would alter the JS contract or requires unavailable runtime support.\n\nPrefer an incremental mixed-mode result over speculative generated code. Keep `definition()` for any remaining DSL elements; delete it only when it is empty and the resolved module name is preserved by `@ExpoModule`.\n\n### 3. Apply the migration\n\nMigrate one semantic group at a time: module naming, functions, properties\u002Fconstants, events, shared objects, then records. Keep the diff narrow.\n\nFollow these invariants:\n\n- Preserve every existing JS-visible name explicitly when Swift naming rules or macro defaults differ.\n- Keep original optional\u002Fdefault behavior. An optional 1.0 record field must not become required merely because 2.0 can express required fields.\n- Do not migrate same-JS-name overloads unless the checked-out macro groups and dispatches them.\n- Do not migrate queue-pinned DSL functions as-is; restructure onto Swift Concurrency or dispatch to the original queue via a continuation, per the async-function rules in `references\u002Fmigration-map.md`.\n- Do not migrate views, unions, synchronous events, or shared-object static functions without verified support.\n- Do not change Kotlin, JS wrappers, or public `.d.ts` files unless the user requested an API change.\n\nAfter each group, search for old DSL entries and call sites that should have moved. Avoid broad formatting or unrelated cleanup.\n\n### When a 2.0 equivalent is missing or a group fails\n\nWhen step 2 classified an item as **Blocked**, or a migrated group fails to build or breaks the contract, do not force it. Stop on that group and:\n\n1. **Ask the user how to proceed** for that item, with two options:\n   - **Co-exist:** keep the item in the 1.0 `definition()` DSL alongside the migrated `@ExpoModule` (mixed mode) and continue with the other groups.\n   - **Revert:** back out the group's edits, leaving it untouched on 1.0, and move on.\n\n   Default to co-existence when mixed mode is verified safe, since it preserves the most progress. Revert when the half-applied change left the module in a non-building state and cannot be salvaged incrementally.\n\n2. **Open a tracking issue on `expo\u002Fexpo`** noting the functionality that 2.0 does not yet cover, so the gap is recorded rather than silently worked around. Use `gh issue create --repo expo\u002Fexpo` and confirm with the user before posting (per repo conventions, do not post outward-facing comments without approval). Include:\n   - the 1.0 member and its JS contract\n   - the specific macro or core hook that is missing (cite the evidence gap from `references\u002Fcompatibility.md`)\n   - the `expo-modules-core` version\u002Fbranch checked out\n\n   Reference the issue in the handoff so the remaining DSL entry is traceable to a known limitation.\n\nKeep going with the groups that do migrate cleanly; one blocked member does not block the rest.\n\n### 4. Verify behavior\n\nRun the narrowest available checks first, then the real integration surface:\n\n1. Build or type-check the Apple module against the target `expo-modules-core`.\n2. Run native unit tests and JS\u002FTS tests.\n3. Build and launch the example app when the repository provides one.\n4. Compare the final exported surface with the inventory from step 1.\n5. Search for stale `Name`, migrated `Function`\u002F`Property`\u002F`Constant`\u002F`Events` entries, old `sendEvent` calls, `@Field`, and duplicate registrations.\n\nExpansion tests alone are insufficient: generated macro code can look correct while failing against mismatched core symbols. If dependencies changed or macro plugin flags are missing, reinstall JS dependencies as appropriate, run the repository's CocoaPods installation workflow, and restart Xcode before diagnosing plugin communication failures.\n\n## Handoff\n\nReport:\n\n- which members moved to 2.0\n- which members intentionally remain in the 1.0 DSL and why\n- any compatibility-sensitive choices, especially event names, record requiredness, constants, and queues\n- the commands run and any verification not completed\n\n## Submitting Feedback\nIf you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:\n```bash\nnpx --yes submit-expo-feedback@latest --category skills --subject \"expo-migrate-module\" \"\u003Cactionable feedback>\"\n```\nOnly submit when you have something specific and actionable to report. Include as much relevant context as possible.\n",{"data":38,"body":40},{"name":4,"description":6,"version":39,"license":29},"1.0.0",{"type":41,"children":42},"root",[43,52,58,65,117,123,173,179,186,198,203,241,246,252,257,262,296,316,322,327,332,379,384,390,402,520,525,531,536,624,629,635,640,663,669,674,752,757],{"type":44,"tag":45,"props":46,"children":48},"element","h1",{"id":47},"migrate-an-expo-module",[49],{"type":50,"value":51},"text","Migrate an Expo Module",{"type":44,"tag":53,"props":54,"children":55},"p",{},[56],{"type":50,"value":57},"Migrate the Swift side of an existing Expo module without changing its observable JS API. Treat the current JS\u002FTypeScript surface and tests as the compatibility contract. Leave Kotlin on the 1.0 DSL unless the user explicitly expands the task.",{"type":44,"tag":59,"props":60,"children":62},"h2",{"id":61},"prerequisite",[63],{"type":50,"value":64},"Prerequisite",{"type":44,"tag":53,"props":66,"children":67},{},[68,70,76,78,84,86,91,93,99,101,107,109,115],{"type":50,"value":69},"The Expo Modules API 2.0 macros require ",{"type":44,"tag":71,"props":72,"children":74},"code",{"className":73},[],[75],{"type":50,"value":8},{"type":50,"value":77}," ",{"type":44,"tag":71,"props":79,"children":81},{"className":80},[],[82],{"type":50,"value":83},"57.0.7",{"type":50,"value":85}," or newer. Before editing, check the target's installed version (",{"type":44,"tag":71,"props":87,"children":89},{"className":88},[],[90],{"type":50,"value":8},{"type":50,"value":92}," in ",{"type":44,"tag":71,"props":94,"children":96},{"className":95},[],[97],{"type":50,"value":98},"package.json",{"type":50,"value":100},"\u002Flockfile, or ",{"type":44,"tag":71,"props":102,"children":104},{"className":103},[],[105],{"type":50,"value":106},"npm ls expo",{"type":50,"value":108},"). If it is older, stop and tell the user to upgrade first; do not attempt the migration against an unsupported version. This is a floor, not a guarantee: the exact macro and core surface still varies within ",{"type":44,"tag":71,"props":110,"children":112},{"className":111},[],[113],{"type":50,"value":114},"57.x",{"type":50,"value":116},", so step 2 must still verify the checked-out source.",{"type":44,"tag":59,"props":118,"children":120},{"id":119},"references",[121],{"type":50,"value":122},"References",{"type":44,"tag":124,"props":125,"children":126},"ul",{},[127,141,153],{"type":44,"tag":128,"props":129,"children":130},"li",{},[131,133,139],{"type":50,"value":132},"Read ",{"type":44,"tag":71,"props":134,"children":136},{"className":135},[],[137],{"type":50,"value":138},"references\u002Fmigration-map.md",{"type":50,"value":140}," before changing source. It contains the 1.0-to-2.0 mappings, semantic traps, and mixed-mode rules.",{"type":44,"tag":128,"props":142,"children":143},{},[144,145,151],{"type":50,"value":132},{"type":44,"tag":71,"props":146,"children":148},{"className":147},[],[149],{"type":50,"value":150},"references\u002Fexample.md",{"type":50,"value":152}," for a full before\u002Fafter walkthrough of one module through mixed mode to a complete migration. Consult it when you need to see how the per-member rules compose.",{"type":44,"tag":128,"props":154,"children":155},{},[156,157,163,165,171],{"type":50,"value":132},{"type":44,"tag":71,"props":158,"children":160},{"className":159},[],[161],{"type":50,"value":162},"references\u002Fcompatibility.md",{"type":50,"value":164}," when the checked-out ",{"type":44,"tag":71,"props":166,"children":168},{"className":167},[],[169],{"type":50,"value":170},"expo-modules-core",{"type":50,"value":172}," version or branch is not known to support every requested macro. It explains how to verify the actual compile-time and runtime surface instead of guessing from an SDK number.",{"type":44,"tag":59,"props":174,"children":176},{"id":175},"workflow",[177],{"type":50,"value":178},"Workflow",{"type":44,"tag":180,"props":181,"children":183},"h3",{"id":182},"_1-establish-the-contract",[184],{"type":50,"value":185},"1. Establish the contract",{"type":44,"tag":53,"props":187,"children":188},{},[189,191,196],{"type":50,"value":190},"Inspect repository instructions and the worktree before editing. Locate the Swift module classes, records, shared objects, native views, JS\u002FTS bindings, tests, example app, podspec, and installed or checked-out ",{"type":44,"tag":71,"props":192,"children":194},{"className":193},[],[195],{"type":50,"value":170},{"type":50,"value":197},".",{"type":44,"tag":53,"props":199,"children":200},{},[201],{"type":50,"value":202},"Inventory every exported item before rewriting it:",{"type":44,"tag":124,"props":204,"children":205},{},[206,211,216,221,226,231,236],{"type":44,"tag":128,"props":207,"children":208},{},[209],{"type":50,"value":210},"module and shared-object JS names",{"type":44,"tag":128,"props":212,"children":213},{},[214],{"type":50,"value":215},"function names, arity, labels, defaults, nullability, sync\u002Fasync behavior, errors, and queue semantics",{"type":44,"tag":128,"props":217,"children":218},{},[219],{"type":50,"value":220},"property names, mutability, and constant caching behavior",{"type":44,"tag":128,"props":222,"children":223},{},[224],{"type":50,"value":225},"event wire names and payload shapes",{"type":44,"tag":128,"props":227,"children":228},{},[229],{"type":50,"value":230},"record field names, defaults, requiredness, and nullability",{"type":44,"tag":128,"props":232,"children":233},{},[234],{"type":50,"value":235},"shared-object constructors and instance\u002Fstatic placement",{"type":44,"tag":128,"props":237,"children":238},{},[239],{"type":50,"value":240},"lifecycle hooks and views",{"type":44,"tag":53,"props":242,"children":243},{},[244],{"type":50,"value":245},"Use the TypeScript declarations and JS call sites to resolve ambiguity. Do not silently \"improve\" requiredness, rename an event, or change sync behavior during a syntax migration.",{"type":44,"tag":180,"props":247,"children":249},{"id":248},"_2-verify-the-available-20-surface",[250],{"type":50,"value":251},"2. Verify the available 2.0 surface",{"type":44,"tag":53,"props":253,"children":254},{},[255],{"type":50,"value":256},"Inspect the macro declarations and matching core hooks in the dependency actually used by the target. Do not assume that all items in the 2.0 design are present because one macro compiles.",{"type":44,"tag":53,"props":258,"children":259},{},[260],{"type":50,"value":261},"Classify each 1.0 item as:",{"type":44,"tag":124,"props":263,"children":264},{},[265,276,286],{"type":44,"tag":128,"props":266,"children":267},{},[268,274],{"type":44,"tag":269,"props":270,"children":271},"strong",{},[272],{"type":50,"value":273},"Migrate:",{"type":50,"value":275}," both its macro and required core runtime support exist.",{"type":44,"tag":128,"props":277,"children":278},{},[279,284],{"type":44,"tag":269,"props":280,"children":281},{},[282],{"type":50,"value":283},"Keep in DSL:",{"type":50,"value":285}," mixed mode preserves it safely, or 2.0 lacks an equivalent.",{"type":44,"tag":128,"props":287,"children":288},{},[289,294],{"type":44,"tag":269,"props":290,"children":291},{},[292],{"type":50,"value":293},"Blocked:",{"type":50,"value":295}," migration would alter the JS contract or requires unavailable runtime support.",{"type":44,"tag":53,"props":297,"children":298},{},[299,301,307,309,315],{"type":50,"value":300},"Prefer an incremental mixed-mode result over speculative generated code. Keep ",{"type":44,"tag":71,"props":302,"children":304},{"className":303},[],[305],{"type":50,"value":306},"definition()",{"type":50,"value":308}," for any remaining DSL elements; delete it only when it is empty and the resolved module name is preserved by ",{"type":44,"tag":71,"props":310,"children":312},{"className":311},[],[313],{"type":50,"value":314},"@ExpoModule",{"type":50,"value":197},{"type":44,"tag":180,"props":317,"children":319},{"id":318},"_3-apply-the-migration",[320],{"type":50,"value":321},"3. Apply the migration",{"type":44,"tag":53,"props":323,"children":324},{},[325],{"type":50,"value":326},"Migrate one semantic group at a time: module naming, functions, properties\u002Fconstants, events, shared objects, then records. Keep the diff narrow.",{"type":44,"tag":53,"props":328,"children":329},{},[330],{"type":50,"value":331},"Follow these invariants:",{"type":44,"tag":124,"props":333,"children":334},{},[335,340,345,350,361,366],{"type":44,"tag":128,"props":336,"children":337},{},[338],{"type":50,"value":339},"Preserve every existing JS-visible name explicitly when Swift naming rules or macro defaults differ.",{"type":44,"tag":128,"props":341,"children":342},{},[343],{"type":50,"value":344},"Keep original optional\u002Fdefault behavior. An optional 1.0 record field must not become required merely because 2.0 can express required fields.",{"type":44,"tag":128,"props":346,"children":347},{},[348],{"type":50,"value":349},"Do not migrate same-JS-name overloads unless the checked-out macro groups and dispatches them.",{"type":44,"tag":128,"props":351,"children":352},{},[353,355,360],{"type":50,"value":354},"Do not migrate queue-pinned DSL functions as-is; restructure onto Swift Concurrency or dispatch to the original queue via a continuation, per the async-function rules in ",{"type":44,"tag":71,"props":356,"children":358},{"className":357},[],[359],{"type":50,"value":138},{"type":50,"value":197},{"type":44,"tag":128,"props":362,"children":363},{},[364],{"type":50,"value":365},"Do not migrate views, unions, synchronous events, or shared-object static functions without verified support.",{"type":44,"tag":128,"props":367,"children":368},{},[369,371,377],{"type":50,"value":370},"Do not change Kotlin, JS wrappers, or public ",{"type":44,"tag":71,"props":372,"children":374},{"className":373},[],[375],{"type":50,"value":376},".d.ts",{"type":50,"value":378}," files unless the user requested an API change.",{"type":44,"tag":53,"props":380,"children":381},{},[382],{"type":50,"value":383},"After each group, search for old DSL entries and call sites that should have moved. Avoid broad formatting or unrelated cleanup.",{"type":44,"tag":180,"props":385,"children":387},{"id":386},"when-a-20-equivalent-is-missing-or-a-group-fails",[388],{"type":50,"value":389},"When a 2.0 equivalent is missing or a group fails",{"type":44,"tag":53,"props":391,"children":392},{},[393,395,400],{"type":50,"value":394},"When step 2 classified an item as ",{"type":44,"tag":269,"props":396,"children":397},{},[398],{"type":50,"value":399},"Blocked",{"type":50,"value":401},", or a migrated group fails to build or breaks the contract, do not force it. Stop on that group and:",{"type":44,"tag":403,"props":404,"children":405},"ol",{},[406,459],{"type":44,"tag":128,"props":407,"children":408},{},[409,414,416,453,457],{"type":44,"tag":269,"props":410,"children":411},{},[412],{"type":50,"value":413},"Ask the user how to proceed",{"type":50,"value":415}," for that item, with two options:",{"type":44,"tag":124,"props":417,"children":418},{},[419,443],{"type":44,"tag":128,"props":420,"children":421},{},[422,427,429,434,436,441],{"type":44,"tag":269,"props":423,"children":424},{},[425],{"type":50,"value":426},"Co-exist:",{"type":50,"value":428}," keep the item in the 1.0 ",{"type":44,"tag":71,"props":430,"children":432},{"className":431},[],[433],{"type":50,"value":306},{"type":50,"value":435}," DSL alongside the migrated ",{"type":44,"tag":71,"props":437,"children":439},{"className":438},[],[440],{"type":50,"value":314},{"type":50,"value":442}," (mixed mode) and continue with the other groups.",{"type":44,"tag":128,"props":444,"children":445},{},[446,451],{"type":44,"tag":269,"props":447,"children":448},{},[449],{"type":50,"value":450},"Revert:",{"type":50,"value":452}," back out the group's edits, leaving it untouched on 1.0, and move on.",{"type":44,"tag":454,"props":455,"children":456},"br",{},[],{"type":50,"value":458},"Default to co-existence when mixed mode is verified safe, since it preserves the most progress. Revert when the half-applied change left the module in a non-building state and cannot be salvaged incrementally.",{"type":44,"tag":128,"props":460,"children":461},{},[462,473,475,481,483,515,518],{"type":44,"tag":269,"props":463,"children":464},{},[465,467],{"type":50,"value":466},"Open a tracking issue on ",{"type":44,"tag":71,"props":468,"children":470},{"className":469},[],[471],{"type":50,"value":472},"expo\u002Fexpo",{"type":50,"value":474}," noting the functionality that 2.0 does not yet cover, so the gap is recorded rather than silently worked around. Use ",{"type":44,"tag":71,"props":476,"children":478},{"className":477},[],[479],{"type":50,"value":480},"gh issue create --repo expo\u002Fexpo",{"type":50,"value":482}," and confirm with the user before posting (per repo conventions, do not post outward-facing comments without approval). Include:",{"type":44,"tag":124,"props":484,"children":485},{},[486,491,503],{"type":44,"tag":128,"props":487,"children":488},{},[489],{"type":50,"value":490},"the 1.0 member and its JS contract",{"type":44,"tag":128,"props":492,"children":493},{},[494,496,501],{"type":50,"value":495},"the specific macro or core hook that is missing (cite the evidence gap from ",{"type":44,"tag":71,"props":497,"children":499},{"className":498},[],[500],{"type":50,"value":162},{"type":50,"value":502},")",{"type":44,"tag":128,"props":504,"children":505},{},[506,508,513],{"type":50,"value":507},"the ",{"type":44,"tag":71,"props":509,"children":511},{"className":510},[],[512],{"type":50,"value":170},{"type":50,"value":514}," version\u002Fbranch checked out",{"type":44,"tag":454,"props":516,"children":517},{},[],{"type":50,"value":519},"Reference the issue in the handoff so the remaining DSL entry is traceable to a known limitation.",{"type":44,"tag":53,"props":521,"children":522},{},[523],{"type":50,"value":524},"Keep going with the groups that do migrate cleanly; one blocked member does not block the rest.",{"type":44,"tag":180,"props":526,"children":528},{"id":527},"_4-verify-behavior",[529],{"type":50,"value":530},"4. Verify behavior",{"type":44,"tag":53,"props":532,"children":533},{},[534],{"type":50,"value":535},"Run the narrowest available checks first, then the real integration surface:",{"type":44,"tag":403,"props":537,"children":538},{},[539,550,555,560,565],{"type":44,"tag":128,"props":540,"children":541},{},[542,544,549],{"type":50,"value":543},"Build or type-check the Apple module against the target ",{"type":44,"tag":71,"props":545,"children":547},{"className":546},[],[548],{"type":50,"value":170},{"type":50,"value":197},{"type":44,"tag":128,"props":551,"children":552},{},[553],{"type":50,"value":554},"Run native unit tests and JS\u002FTS tests.",{"type":44,"tag":128,"props":556,"children":557},{},[558],{"type":50,"value":559},"Build and launch the example app when the repository provides one.",{"type":44,"tag":128,"props":561,"children":562},{},[563],{"type":50,"value":564},"Compare the final exported surface with the inventory from step 1.",{"type":44,"tag":128,"props":566,"children":567},{},[568,570,576,578,584,586,592,593,599,600,606,608,614,616,622],{"type":50,"value":569},"Search for stale ",{"type":44,"tag":71,"props":571,"children":573},{"className":572},[],[574],{"type":50,"value":575},"Name",{"type":50,"value":577},", migrated ",{"type":44,"tag":71,"props":579,"children":581},{"className":580},[],[582],{"type":50,"value":583},"Function",{"type":50,"value":585},"\u002F",{"type":44,"tag":71,"props":587,"children":589},{"className":588},[],[590],{"type":50,"value":591},"Property",{"type":50,"value":585},{"type":44,"tag":71,"props":594,"children":596},{"className":595},[],[597],{"type":50,"value":598},"Constant",{"type":50,"value":585},{"type":44,"tag":71,"props":601,"children":603},{"className":602},[],[604],{"type":50,"value":605},"Events",{"type":50,"value":607}," entries, old ",{"type":44,"tag":71,"props":609,"children":611},{"className":610},[],[612],{"type":50,"value":613},"sendEvent",{"type":50,"value":615}," calls, ",{"type":44,"tag":71,"props":617,"children":619},{"className":618},[],[620],{"type":50,"value":621},"@Field",{"type":50,"value":623},", and duplicate registrations.",{"type":44,"tag":53,"props":625,"children":626},{},[627],{"type":50,"value":628},"Expansion tests alone are insufficient: generated macro code can look correct while failing against mismatched core symbols. If dependencies changed or macro plugin flags are missing, reinstall JS dependencies as appropriate, run the repository's CocoaPods installation workflow, and restart Xcode before diagnosing plugin communication failures.",{"type":44,"tag":59,"props":630,"children":632},{"id":631},"handoff",[633],{"type":50,"value":634},"Handoff",{"type":44,"tag":53,"props":636,"children":637},{},[638],{"type":50,"value":639},"Report:",{"type":44,"tag":124,"props":641,"children":642},{},[643,648,653,658],{"type":44,"tag":128,"props":644,"children":645},{},[646],{"type":50,"value":647},"which members moved to 2.0",{"type":44,"tag":128,"props":649,"children":650},{},[651],{"type":50,"value":652},"which members intentionally remain in the 1.0 DSL and why",{"type":44,"tag":128,"props":654,"children":655},{},[656],{"type":50,"value":657},"any compatibility-sensitive choices, especially event names, record requiredness, constants, and queues",{"type":44,"tag":128,"props":659,"children":660},{},[661],{"type":50,"value":662},"the commands run and any verification not completed",{"type":44,"tag":59,"props":664,"children":666},{"id":665},"submitting-feedback",[667],{"type":50,"value":668},"Submitting Feedback",{"type":44,"tag":53,"props":670,"children":671},{},[672],{"type":50,"value":673},"If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:",{"type":44,"tag":675,"props":676,"children":681},"pre",{"className":677,"code":678,"language":679,"meta":680,"style":680},"language-bash shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","npx --yes submit-expo-feedback@latest --category skills --subject \"expo-migrate-module\" \"\u003Cactionable feedback>\"\n","bash","",[682],{"type":44,"tag":71,"props":683,"children":684},{"__ignoreMap":680},[685],{"type":44,"tag":686,"props":687,"children":690},"span",{"class":688,"line":689},"line",1,[691,697,703,708,713,718,723,729,733,738,742,747],{"type":44,"tag":686,"props":692,"children":694},{"style":693},"--shiki-light:#E2931D;--shiki-default:#FFCB6B;--shiki-dark:#FFCB6B",[695],{"type":50,"value":696},"npx",{"type":44,"tag":686,"props":698,"children":700},{"style":699},"--shiki-light:#91B859;--shiki-default:#C3E88D;--shiki-dark:#C3E88D",[701],{"type":50,"value":702}," --yes",{"type":44,"tag":686,"props":704,"children":705},{"style":699},[706],{"type":50,"value":707}," submit-expo-feedback@latest",{"type":44,"tag":686,"props":709,"children":710},{"style":699},[711],{"type":50,"value":712}," --category",{"type":44,"tag":686,"props":714,"children":715},{"style":699},[716],{"type":50,"value":717}," skills",{"type":44,"tag":686,"props":719,"children":720},{"style":699},[721],{"type":50,"value":722}," --subject",{"type":44,"tag":686,"props":724,"children":726},{"style":725},"--shiki-light:#39ADB5;--shiki-default:#89DDFF;--shiki-dark:#89DDFF",[727],{"type":50,"value":728}," \"",{"type":44,"tag":686,"props":730,"children":731},{"style":699},[732],{"type":50,"value":4},{"type":44,"tag":686,"props":734,"children":735},{"style":725},[736],{"type":50,"value":737},"\"",{"type":44,"tag":686,"props":739,"children":740},{"style":725},[741],{"type":50,"value":728},{"type":44,"tag":686,"props":743,"children":744},{"style":699},[745],{"type":50,"value":746},"\u003Cactionable feedback>",{"type":44,"tag":686,"props":748,"children":749},{"style":725},[750],{"type":50,"value":751},"\"\n",{"type":44,"tag":53,"props":753,"children":754},{},[755],{"type":50,"value":756},"Only submit when you have something specific and actionable to report. Include as much relevant context as possible.",{"type":44,"tag":758,"props":759,"children":760},"style",{},[761],{"type":50,"value":762},"html .light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html.light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"items":764,"total":870},[765,783,798,813,827,841,859],{"slug":766,"name":766,"fn":767,"description":768,"org":769,"tags":770,"stars":26,"repoUrl":27,"updatedAt":782},"eas-app-stores","deploy and submit Expo apps to stores","EAS service (paid). Deploy Expo apps to the app stores with EAS - build and submit to the iOS App Store, Google Play Store, and TestFlight, configure eas.json build and submit profiles, manage app versions and build numbers, and publish App Store metadata and ASO. Use whenever the user wants to deploy, release, or ship an app to production or the app stores, is preparing a production build, running eas build or eas submit, shipping to TestFlight, bumping version or build numbers, or setting up store listing metadata. For deploying an Expo website or API routes, use the eas-hosting skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[771,774,777,778,781],{"name":772,"slug":773,"type":13},"Android","android",{"name":775,"slug":776,"type":13},"Deployment","deployment",{"name":9,"slug":8,"type":13},{"name":779,"slug":780,"type":13},"iOS","ios",{"name":18,"slug":19,"type":13},"2026-07-24T05:36:44.164663",{"slug":784,"name":784,"fn":785,"description":786,"org":787,"tags":788,"stars":26,"repoUrl":27,"updatedAt":797},"eas-hosting","deploy Expo websites to EAS Hosting","EAS service (paid). Deploy Expo websites and Expo Router API routes to EAS Hosting - export the web bundle, run eas deploy for production and PR preview URLs, manage environment secrets and custom domains, and work within the Cloudflare Workers runtime. Also covers authoring API routes (+api.ts handlers, HTTP methods, request handling, CORS). Use when deploying an Expo web app or API routes, setting up EAS Hosting, or configuring hosting environments and domains. Not for native builds or store releases - use the eas-app-stores skill for those.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[789,790,791,794],{"name":775,"slug":776,"type":13},{"name":9,"slug":8,"type":13},{"name":792,"slug":793,"type":13},"Frontend","frontend",{"name":795,"slug":796,"type":13},"Web Development","web-development","2026-07-24T05:36:40.193701",{"slug":799,"name":799,"fn":800,"description":801,"org":802,"tags":803,"stars":26,"repoUrl":27,"updatedAt":812},"eas-observe","configure EAS Observe for Expo apps","EAS service (paid). Use for anything related to EAS Observe - adding `expo-observe` to an Expo project (AppMetricsRoot\u002FObserveRoot HOC, markInteractive, the useObserve hook, the Expo Router \u002F React Navigation integrations for per-route metrics, and user-defined events via `Observe.logEvent`), querying via the EAS CLI (`eas observe:metrics-summary`, `observe:metrics`, `observe:routes`, `observe:events`, `observe:versions`), or interpreting the resulting metrics (cold\u002Fwarm launch, TTR, TTI, navigation cold\u002Fwarm TTR, update download, and the TTI frameRate params for triaging slow startups).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[804,805,806,809],{"name":9,"slug":8,"type":13},{"name":18,"slug":19,"type":13},{"name":807,"slug":808,"type":13},"Observability","observability",{"name":810,"slug":811,"type":13},"React Native","react-native","2026-07-24T05:36:45.220605",{"slug":814,"name":814,"fn":815,"description":816,"org":817,"tags":818,"stars":26,"repoUrl":27,"updatedAt":826},"eas-simulator","run and control remote iOS and Android simulators","EAS service (paid). Run and control a user's app on a remote iOS\u002FAndroid simulator hosted on EAS cloud. Read before running any `eas simulator:*` commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas simulator to run\u002Finstall\u002Fscreenshot my app', 'I'm on Linux\u002FCursor and need an iOS device', 'no sim on this box \u002F headless CI', 'let an agent click through my app and screenshot it', 'test my dev build on a remote sim with live reload', 'stream a sim to my browser' - even when they don't say 'EAS Simulator' or 'cloud'. On a host WITHOUT a local simulator (Linux, CI, cloud sandbox) it's the default; on macOS, do NOT auto-trigger for a plain 'run on the simulator' - use it only for a cloud\u002Fremote\u002Fshareable sim, an iOS version they lack, or an agent-driven session. NOT for local sims (expo run:ios, Xcode, Android Studio), EAS Build\u002FUpdate, web preview, or physical devices.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[819,820,823,824,825],{"name":772,"slug":773,"type":13},{"name":821,"slug":822,"type":13},"CLI","cli",{"name":9,"slug":8,"type":13},{"name":779,"slug":780,"type":13},{"name":18,"slug":19,"type":13},"2026-07-31T05:52:18.602058",{"slug":828,"name":828,"fn":829,"description":830,"org":831,"tags":832,"stars":26,"repoUrl":27,"updatedAt":840},"eas-update-insights","check health of EAS Updates","EAS service (paid). Check the health of published EAS Update: crash rates, install\u002Flaunch counts, unique users, payload size, and the split between embedded and OTA users per channel. Use when the user asks how an update is performing, whether a rollout is healthy, how many users are on the embedded build vs OTA, or wants to gate CI on update health.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[833,836,837,838,839],{"name":834,"slug":835,"type":13},"Analytics","analytics",{"name":775,"slug":776,"type":13},{"name":9,"slug":8,"type":13},{"name":18,"slug":19,"type":13},{"name":807,"slug":808,"type":13},"2026-07-24T05:36:50.17095",{"slug":842,"name":842,"fn":843,"description":844,"org":845,"tags":846,"stars":26,"repoUrl":27,"updatedAt":858},"eas-workflows","configure EAS workflows for Expo projects","EAS service (paid). Helps understand and write EAS workflow YAML files for Expo projects. Use this skill when the user asks about CI\u002FCD or workflows in an Expo or EAS context, mentions .eas\u002Fworkflows\u002F, or wants help with EAS build pipelines or deployment automation.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[847,850,853,854,855],{"name":848,"slug":849,"type":13},"Automation","automation",{"name":851,"slug":852,"type":13},"CI\u002FCD","ci-cd",{"name":775,"slug":776,"type":13},{"name":9,"slug":8,"type":13},{"name":856,"slug":857,"type":13},"YAML","yaml","2026-07-24T05:36:43.205514",{"slug":860,"name":860,"fn":861,"description":862,"org":863,"tags":864,"stars":26,"repoUrl":27,"updatedAt":869},"expo-app-clip","add iOS App Clip targets to Expo","Framework (OSS). Add an iOS App Clip target to an Expo app. Use when the user mentions App Clip, AASA, apple-app-site-association, appclips, smart app banner, or wants to ship a lightweight iOS Clip invoked from a URL alongside their parent app.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[865,866,867,868],{"name":9,"slug":8,"type":13},{"name":779,"slug":780,"type":13},{"name":18,"slug":19,"type":13},{"name":810,"slug":811,"type":13},"2026-07-24T05:36:46.195935",22,{"items":872,"total":996},[873,881,888,895,903,911,919,926,941,959,974,985],{"slug":766,"name":766,"fn":767,"description":768,"org":874,"tags":875,"stars":26,"repoUrl":27,"updatedAt":782},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[876,877,878,879,880],{"name":772,"slug":773,"type":13},{"name":775,"slug":776,"type":13},{"name":9,"slug":8,"type":13},{"name":779,"slug":780,"type":13},{"name":18,"slug":19,"type":13},{"slug":784,"name":784,"fn":785,"description":786,"org":882,"tags":883,"stars":26,"repoUrl":27,"updatedAt":797},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[884,885,886,887],{"name":775,"slug":776,"type":13},{"name":9,"slug":8,"type":13},{"name":792,"slug":793,"type":13},{"name":795,"slug":796,"type":13},{"slug":799,"name":799,"fn":800,"description":801,"org":889,"tags":890,"stars":26,"repoUrl":27,"updatedAt":812},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[891,892,893,894],{"name":9,"slug":8,"type":13},{"name":18,"slug":19,"type":13},{"name":807,"slug":808,"type":13},{"name":810,"slug":811,"type":13},{"slug":814,"name":814,"fn":815,"description":816,"org":896,"tags":897,"stars":26,"repoUrl":27,"updatedAt":826},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[898,899,900,901,902],{"name":772,"slug":773,"type":13},{"name":821,"slug":822,"type":13},{"name":9,"slug":8,"type":13},{"name":779,"slug":780,"type":13},{"name":18,"slug":19,"type":13},{"slug":828,"name":828,"fn":829,"description":830,"org":904,"tags":905,"stars":26,"repoUrl":27,"updatedAt":840},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[906,907,908,909,910],{"name":834,"slug":835,"type":13},{"name":775,"slug":776,"type":13},{"name":9,"slug":8,"type":13},{"name":18,"slug":19,"type":13},{"name":807,"slug":808,"type":13},{"slug":842,"name":842,"fn":843,"description":844,"org":912,"tags":913,"stars":26,"repoUrl":27,"updatedAt":858},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[914,915,916,917,918],{"name":848,"slug":849,"type":13},{"name":851,"slug":852,"type":13},{"name":775,"slug":776,"type":13},{"name":9,"slug":8,"type":13},{"name":856,"slug":857,"type":13},{"slug":860,"name":860,"fn":861,"description":862,"org":920,"tags":921,"stars":26,"repoUrl":27,"updatedAt":869},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[922,923,924,925],{"name":9,"slug":8,"type":13},{"name":779,"slug":780,"type":13},{"name":18,"slug":19,"type":13},{"name":810,"slug":811,"type":13},{"slug":927,"name":927,"fn":928,"description":929,"org":930,"tags":931,"stars":26,"repoUrl":27,"updatedAt":940},"expo-brownfield","integrate Expo and React Native into native apps","Framework (OSS). Integrate Expo and React Native into an existing native iOS or Android app. Use when the user mentions brownfield, embedding React Native in a native app, AAR\u002FXCFramework, or adding Expo to an existing Kotlin\u002FSwift project. Covers both the isolated approach and the integrated approach.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[932,933,934,937,938,939],{"name":772,"slug":773,"type":13},{"name":9,"slug":8,"type":13},{"name":935,"slug":936,"type":13},"Integrations","integrations",{"name":779,"slug":780,"type":13},{"name":18,"slug":19,"type":13},{"name":810,"slug":811,"type":13},"2026-07-24T05:36:39.682299",{"slug":942,"name":942,"fn":943,"description":944,"org":945,"tags":946,"stars":26,"repoUrl":27,"updatedAt":958},"expo-data-fetching","fetch and manage data in Expo apps","Framework (OSS). Use when implementing or debugging ANY network request, API call, or data fetching. Covers fetch API, React Query, SWR, error handling, caching, offline support, and Expo Router data loaders (`useLoaderData`).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[947,950,953,954,955],{"name":948,"slug":949,"type":13},"API Development","api-development",{"name":951,"slug":952,"type":13},"Caching","caching",{"name":9,"slug":8,"type":13},{"name":18,"slug":19,"type":13},{"name":956,"slug":957,"type":13},"React","react","2026-07-24T05:36:42.177188",{"slug":960,"name":960,"fn":961,"description":962,"org":963,"tags":964,"stars":26,"repoUrl":27,"updatedAt":973},"expo-dev-client","build and distribute Expo development clients","Framework (OSS). Build and distribute Expo development clients locally or via TestFlight for internal testing. For production TestFlight releases and store submission, use the eas-app-stores skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[965,966,967,968,969,972],{"name":772,"slug":773,"type":13},{"name":775,"slug":776,"type":13},{"name":9,"slug":8,"type":13},{"name":779,"slug":780,"type":13},{"name":970,"slug":971,"type":13},"Local Development","local-development",{"name":18,"slug":19,"type":13},"2026-07-24T05:36:51.160719",{"slug":975,"name":975,"fn":976,"description":977,"org":978,"tags":979,"stars":26,"repoUrl":27,"updatedAt":984},"expo-dom","run web components in native apps","Framework (OSS). Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally. For the end-to-end migration of a whole web app, use the expo-web-to-native skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[980,981,982,983],{"name":9,"slug":8,"type":13},{"name":792,"slug":793,"type":13},{"name":18,"slug":19,"type":13},{"name":810,"slug":811,"type":13},"2026-07-24T05:36:41.176872",{"slug":986,"name":986,"fn":987,"description":988,"org":989,"tags":990,"stars":26,"repoUrl":27,"updatedAt":995},"expo-examples","integrate Expo example projects","Framework (OSS). Expo's official example projects - the expo\u002Fexamples repo of ~70 `with-*` integrations (Stripe, Clerk, Supabase, OpenAI, maps, Reanimated, SQLite, Skia, NativeWind, and more). Use when integrating a third-party library or service into an existing Expo app and you want the canonical, version-matched pattern to adapt, or when scaffolding a new project from one with `npx create-expo --example`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[991,992,993,994],{"name":9,"slug":8,"type":13},{"name":935,"slug":936,"type":13},{"name":18,"slug":19,"type":13},{"name":810,"slug":811,"type":13},"2026-07-24T05:36:35.174379",24]