@ai-sdk/react@4.0.162: experimental_MCPAppRenderer deprecated

@ai-sdk/react 4.0.162 marks the named export experimental_MCPAppRenderer as deprecated and points to MCPAppRenderer instead. The old name is still exported and still works, so nothing breaks at this release. You are affected if your code imports experimental_MCPAppRenderer from @ai-sdk/react.

What changed

• Deprecated export. The 4.0.162 declarations carry a deprecation notice on experimental_MCPAppRenderer that says to use MCPAppRenderer. In 4.0.161 the package exported the component only under the experimental name. In 4.0.162 it exports MCPAppRenderer and keeps the old name as an alias.
• Nothing else to act on. The changelog also lists other MCP APIs graduating to stable, among them StdioMCPTransport. Emendant carries one change for this release, the deprecation above, and reports nothing for the rest.

Before and after

The scan matches a named import of the old name from @ai-sdk/react:

// before
import { experimental_MCPAppRenderer } from '@ai-sdk/react';

// after
import { MCPAppRenderer } from '@ai-sdk/react';

Uses of the component in that file move to the new name with the import. The patch is assisted, so the shape above is what the 4.0.162 declarations point to, not a fixed text rewrite. This release has no other rewrites.

Migration guidance and its limits

Run emendant scan to list the files that import experimental_MCPAppRenderer from @ai-sdk/react, then run emendant fix. The finding has an assisted patch, so emendant fix writes it only when you name a model provider. Without one, the finding is reported and nothing is changed. This release has no deterministic patch, and no finding in it is report only.

Each patch is checked with your typecheck and your tests. Read the patch header to see which checks passed. The patch is meant to change the name only, never what the code does. Where a file re-exports the old name for other modules, or the release gives no clear replacement for how the component is used, review the surrounding code yourself. A patch may not be available there.

The old name still works at 4.0.162, so you can schedule the rename rather than rush it.

A clean scan covers named imports of experimental_MCPAppRenderer from @ai-sdk/react. The same name imported from another module, such as a local compatibility file, is not reported. A clean scan also says nothing about the other API changes the changelog describes, because this page covers the one deprecation the feed carries.

What Emendant detects, fixes and verifies

1 change in @ai-sdk/react 4.0.162. 0 automatic fixes, 1 fixes requiring a model provider you choose, 0 report only. Each patch states which checks passed. Understand patch evidence.

emendant explain <change-id> prints any row's entry, guidance and sources at the terminal.

Coverage

Requires emendant@0.1.0 or later. Run emendant feed update to get the latest coverage.

Primary sources

• @ai-sdk/react@4.0.162npm registry, the published package
• @ai-sdk/react@4.0.161npm registry, the published package

Scan your repository

Find affected code without editing your files.

npx emendant scan

Then npx emendant fix writes the patches the table says exist. The getting started guide covers the flags and the patch grades.

Related release pages

• Earlier @ai-sdk/react release: @ai-sdk/react 2.0.0: useChat migration
• Later @ai-sdk/react release: @ai-sdk/react@4.0.167: Experimental_UseRealtimeOptions members changed

Every @ai-sdk/react release page is listed on one page.