full-send install fails due to cli error

[pradelkai]

When trying to install the full-send example, the process fails, apparently due to a CLI issue:

0 verbose cli /Users/kaipradel/.nvm/versions/node/v22.16.0/bin/node /Users/kaipradel/Documents/GitHub/superdone-app/node_modules/.bin/npm
1 info using npm@10.9.3
2 info using node@v22.16.0
3 silly config load:file:/Users/kaipradel/Documents/GitHub/superdone-app/node_modules/npm/npmrc
4 silly config load:file:/Users/kaipradel/Documents/GitHub/superdone-app/.npmrc
5 silly config load:file:/Users/kaipradel/.npmrc
6 silly config load:file:/Users/kaipradel/.nvm/versions/node/v22.16.0/etc/npmrc
7 verbose title npm install @tambo-ai/react radix-ui streamdown highlight.js @tambo-ai/typescript-sdk dompurify json-stringify-pretty-compact @tambo-ai/reac$
8 verbose argv "install" "@tambo-ai/react" "radix-ui" "streamdown" "highlight.js" "@tambo-ai/typescript-sdk" "dompurify" "json-stringify-pretty-compact" "@t$
9 verbose logfile logs-max:10 dir:/Users/kaipradel/.npm/_logs/2025-11-20T12_17_09_663Z-
10 verbose logfile /Users/kaipradel/.npm/_logs/2025-11-20T12_17_09_663Z-debug-0.log
11 silly logfile start cleaning logs, removing 1 files
12 silly packumentCache heap:4345298944 maxSize:1086324736 maxEntrySize:543162368
13 silly logfile done cleaning log files
14 verbose stack Error: Could not read package.json: Error: ENOENT: no such file or directory, open '/Users/kaipradel/Documents/GitHub/superdone-app/@tambo-$
14 verbose stack     at async open (node:internal/fs/promises:633:25)
14 verbose stack     at async readFile (node:internal/fs/promises:1237:14)
14 verbose stack     at async read (/Users/kaipradel/Documents/GitHub/superdone-app/node_modules/npm/node_modules/@npmcli/package-json/lib/read-package.js:9$
14 verbose stack     at async PackageJson.load (/Users/kaipradel/Documents/GitHub/superdone-app/node_modules/npm/node_modules/@npmcli/package-json/lib/index$
14 verbose stack     at async PackageJson.normalize (/Users/kaipradel/Documents/GitHub/superdone-app/node_modules/npm/node_modules/@npmcli/package-json/lib/$
14 verbose stack     at async /Users/kaipradel/Documents/GitHub/superdone-app/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.j$
14 verbose stack     at async Promise.all (index 7)
14 verbose stack     at async #add (/Users/kaipradel/Documents/GitHub/superdone-app/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-$
14 verbose stack     at async #applyUserRequestsToNode (/Users/kaipradel/Documents/GitHub/superdone-app/node_modules/npm/node_modules/@npmcli/arborist/lib/a$
14 verbose stack     at async #applyUserRequests (/Users/kaipradel/Documents/GitHub/superdone-app/node_modules/npm/node_modules/@npmcli/arborist/lib/arboris$
15 error code ENOENT
16 error syscall open

The cli is running this:

npm install @tambo-ai/react radix-ui streamdown highlight.js \
  @tambo-ai/typescript-sdk dompurify json-stringify-pretty-compact \
  @tambo-ai/react/mcp

And npm is blowing up with:
enoent Could not read package.json: Error: ENOENT: no such file or directory, open ‘/Users/…/superdone-app/@tambo-ai/react/mcp/package.json’

Key point:

• @tambo-ai/react is a real npm package. 
• @tambo-ai/react/mcp is meant to be an import subpath, e.g.:

The CLI is incorrectly trying to npm install @tambo-ai/react/mcp, and npm interprets that as a local path ./@tambo-ai/react/mcp, hence the ENOENT in your project directory.

So: this is a bug / rough edge in the current Tambo CLI when installing MCP-related components into an existing app.

[alecf]

thanks! We already have a fix for this coming out shortly!