| name | evo-app-migrate-react |
| description | Migrate an application from @ebay/ui-core-react to @evo-web/react. Run this in your application repo (not in the evo-web monorepo). Receives an optional component name to migrate (e.g. /evo-app-migrate-react ebay-button), or migrates all supported components if no argument is given. |
Migrate app: @ebay/ui-core-react → @evo-web/react
Argument: $ARGUMENTS — specific component (e.g. ebay-button), or empty to migrate all.
Step 0 — Scope the work first
- Confirm
@ebay/ui-core-react is in package.json.
- Find all affected files:
grep -r "@ebay/ui-core-react" --include="*.tsx" --include="*.ts" --include="*.jsx" --include="*.js" -l
- If
$ARGUMENTS is set, filter to only files importing that component.
- List every affected file before modifying anything.
Step 1 — Update package.json
Add @evo-web/react at latest. Remove @ebay/ui-core-react only if all its components are now migrated.
+ "@evo-web/react": "latest",
- "@ebay/ui-core-react": "x.x.x", // only if fully replaced
Step 2 — Apply global renames (all components)
Import path: map each @ebay/ui-core-react subpath to the matching @evo-web/react subpath, dropping the ebay- prefix from the subpath name:
- import { EbayButton } from "@ebay/ui-core-react/ebay-button";
+ import { EvoButton } from "@evo-web/react/button";
For icons:
- import { EbayIconCart16 } from "@ebay/ui-core-react/icons/ebay-icon-cart-16";
+ import { EvoIconCart16 } from "@evo-web/react/icons/cart-16";
Component names: Ebay prefix → Evo prefix (e.g. EbayButton → EvoButton, EbayButtonCell → EvoButtonCell). Types follow the same pattern (EbayButtonProps → EvoButtonProps).
Refs: ref works as a native prop in @evo-web/react — no change needed in usage.
Step 3 — Apply per-component prop changes
If a component is not listed below, it has not been migrated yet — keep using @ebay/ui-core-react for it and tell the user.
When migrating a listed component, read the linked file completely and apply the component-specific changes in addition to the global renames from Step 2.
Step 4 — Verify
- Type-check:
tsc --noEmit (or equivalent).
- Run the app's test suite.
- Smoke-test migrated components in the browser.
Rules
- Do not migrate components not listed in Step 3 — flag them to the user instead.
- Do not guess at prop renames — if a prop in the app isn't listed above, keep it and flag it.
- Do not upgrade any other dependencies.
