Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | # @composio/vercel + AI SDK v7 Compatibility Test |
| 2 | |
| 3 | Verifies that `@composio/vercel` installs, typechecks, and executes wrapped tools with `ai@7`. |
| 4 | |
| 5 | ## Background |
| 6 | |
| 7 | `@composio/vercel` declares `ai` as a peer dependency across multiple majors (`^6.0.0 || ^7.0.0`). This suite guards the AI SDK **v7** arm of that range, including the v7-specific `ToolExecutionOptions` shape passed to `tool.execute`. The v6 arm is covered by the sibling `vercel-ai-sdk-v6` suite. |
| 8 | |
| 9 | ## What It Tests |
| 10 | |
| 11 | | Marker | Description | |
| 12 | | ---------------------------------------------- | --------------------------------------------------------------------- | |
| 13 | | `vercel ai sdk compatibility typecheck passed` | The packed provider typechecks against `ai@7` (`fixtures/index.ts`) | |
| 14 | | `WRAPPED_TOOL_INPUT_SCHEMA_OK` | `wrapTool` returns an AI SDK tool with `inputSchema` + `execute` | |
| 15 | | `OBJECT_INPUT_EXECUTION_OK` | Object inputs are forwarded to `executeTool` | |
| 16 | | `STRING_INPUT_EXECUTION_OK` | JSON-string inputs are normalized before `executeTool` | |
| 17 | | `V7_EXECUTION_OPTIONS_OK` | A wrapped tool accepts AI SDK v7 `ToolExecutionOptions` | |
| 18 | | `SOURCE_SCHEMA_OK` | The source JSON Schema reaches `inputSchema`; Zod validates arguments | |
| 19 | | `TOOL_SET_OK` | `wrapTools` produces a `ToolSet`-compatible collection | |
| 20 | |
| 21 | ## Fixture |
| 22 | |
| 23 | ``` |
| 24 | fixtures/ |
| 25 | ├── index.mjs # Executed at runtime: wraps a tool and asserts execution behavior |
| 26 | ├── index.ts # Type-only (tsc --noEmit): asserts the provider's types line up with ai@7 |
| 27 | └── package.json # Declares @composio/core (linked), ai@7, typescript, zod |
| 28 | ``` |
| 29 | |
| 30 | The provider is installed the way consumers get it: `npm pack` of `@composio/vercel`, then install the resulting tarball — so the published `dist` and `peerDependencies` are exercised, not the workspace source. |
| 31 | |
| 32 | ## Setup |
| 33 | |
| 34 | The `setup` phase runs `npm run install:vercel && npm run typecheck` in a Docker volume, then the fixture (`index.mjs`) runs with the installed `node_modules` mounted read-only. |
| 35 | |
| 36 | ## Isolation Tool |
| 37 | |
| 38 | **Docker** with Node.js versions: 22.23.5, 24.22.3, 26.13.1. |
| 39 | |
| 40 | ## Running |
| 41 | |
| 42 | ```bash |
| 43 | pnpm test:e2e |
| 44 | ``` |