API symbol index

You pasted an identifier from a build error and want to know whether anything here rewrites it. This page maps 89 API symbols across 11 providers onto the migration pack that matches them, and states what each rewrite does. Use your browser's find-in-page.

What a row here proves, and what it does not

Every row is extracted mechanically from the detect pattern of a shipped rewrite rule — the same pattern mendapi fix dispatches on when it walks your files. There is no hand-maintained symbol list: 89 rules across 47 packs produced this table at build time, so a symbol cannot appear here unless a shipped rule matches it, and cannot survive here after that rule is deleted.

What that does not prove is that the pack rewrites your particular call site. A rule matches a symbol; whether it can safely transform the surrounding expression depends on how your code is shaped. The honest way to find out takes two commands and touches nothing:

npx mendapi sync
npx mendapi fix --repo . --migration <pack-name>

The second command prints a unified diff and exits. Nothing is written without --apply. If the pack does not match your shapes, the diff is empty — which is a real answer, not a failure.

Symbols

A symbol listed against more than one pack is genuinely touched by more than one upstream change — the same field withdrawn from two API surfaces, for example. Both packs are listed rather than one being picked for you.

Full pack detail, including the change IDs each pack covers and its API-surface anchors, is on Migration packs. For terminology used in the rewrite descriptions, see the glossary.