The @ai-sdk/vue 2.0 migration changes how a Vue application owns chat state. Code that imports useChat, useAssistant or the old message types needs review. The release also changes the result and callbacks of useCompletion, so check completion components as well as chat components.

Choose your migration path

Check your upgrade

Check your installed version in the manifest and lockfile, then read the release pages your upgrade crosses. Run npx emendant scan to find supported changes in TypeScript and JavaScript source without editing your files. Use npx emendant fix --dry-run to preview deterministic patches where available. The preview does not install dependencies, run your checks or call a model. Assisted patches need a named model provider and a fix run without --dry-run. After updating dependencies, run your typecheck and tests and review the patch grades in the fix guide.

Coverage and limits

The listed findings have possible assisted fixes and need a named model provider. A patch is not a complete component migration. Emendant scans TypeScript and JavaScript source, so review Vue templates and the server side of your chat flow yourself. The 4.0 release exports useChat again, so check that target before choosing the 2.0 class migration. This hub does not claim scan coverage of later Vue binding releases.

The linked release pages list covered findings, possible fixes and tagged sources. A clean scan does not prove that every migration step is complete. Read the supported projects guide for the scan's scope.

@ai-sdk/vue release pages

Releases without a page here may still be in the feed. Run emendant feed status to see what your snapshot holds.