migrate-waniwani-sdk-0.19-to-0.20
Migrate @waniwani/sdk 0.19 → 0.20
A self-contained migration for the single hop from 0.19.x to 0.20.x. It covers only that jump; for other version boundaries use the matching migrate-waniwani-sdk-<from>-to-<to> skill, or the general procedure in the SDK's changelog.
Precondition: the project is on @waniwani/sdk@0.19.x. If it is on an older version, migrate up to 0.19 first (each jump ships its own migration skill); if it is already on 0.20+, there is nothing to do here.
What 0.20 changes
0.12.0 moved the MCP-widget-in-host stack and the chat-server BFF adapters to @waniwani/sdk/legacy* while the old paths kept re-exporting every symbol, so nothing broke. 0.20.0 deletes the whole tier. There is no shim and no deprecation window left: these surface as module-resolution errors, not warnings.
Entry points that no longer exist:
| Entry point | Held |
|---|---|
@waniwani/sdk/legacy |
createTool, createResource, registerTools, ToolConfig, ToolHandler, ToolHandlerContext, ToolToolCallback, ResourceConfig, RegisteredResource, WidgetCSP |
@waniwani/sdk/legacy/react |
WidgetProvider, useWidgetClient, useToolOutput, useToolResponseMetadata, useCallTool, useSendFollowUp, useFlowAction, useUpdateModelContext, useDisplayMode, useRequestDisplayMode, useTheme, useLocale, useSafeArea, useMaxHeight, useWidgetState, useOpenExternal, useIsChatGptApp, InitializeNextJsInIframe, LoadingWidget, DevModeProvider, the mock helpers, detectPlatform, isMCPApps, isOpenAI |
@waniwani/sdk/legacy/next-js, @waniwani/sdk/next-js |
toNextJsHandler |
@waniwani/sdk/legacy/express-js, @waniwani/sdk/express-js |
toExpressJsHandler |
@waniwani/sdk/chat/server |
ApiHandler, ApiHandlerOptions, BeforeRequestContext, BeforeRequestResult, ClientVisitorContext, VisitorMeta, WebSearchConfig, GeoLocation, extractGeoFromHeaders |