fix(ai-mcp): add shims to bin bundle for CJS dynamic-require compat (#754)

* fix(ai-mcp): add shims to bin bundle for CJS dynamic-require compat

json-schema-to-typescript (inlined via noExternal) uses dynamic require()
calls internally. When bundled into an ESM output the global require is
absent, causing the CLI to crash on startup with
"Dynamic require of 'fs' is not supported" before it can parse any args.

shims: true makes tsup inject a createRequire-based shim at the top of the
bundle so CJS dependencies can call require() safely from within the ESM
output.

Fixes #753

* chore: add changeset for ai-mcp CLI dynamic-require shim fix

* ci: apply automated fixes

---------

Co-authored-by: Alem Tuzlak <t.zlak@hotmail.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>

Author: 3 people

.changeset/mcp-cli-dynamic-require-shims.md

@@ -0,0 +1,5 @@
+---
+'@tanstack/ai-mcp': patch
+---
+
+Fix `@tanstack/ai-mcp` CLI crashing on startup with `Error: Dynamic require of "fs" is not supported`. The CLI ships as an ESM bundle with `json-schema-to-typescript` inlined, which uses CJS `require()` internally. Enabling tsup's `shims` option injects a `createRequire(import.meta.url)` shim so those `require()` calls resolve correctly.

packages/ai-mcp/tsup.bin.config.ts

@@ -10,5 +10,8 @@ export default defineConfig({
   noExternal: ['json-schema-to-typescript', 'jiti'],
   // Keep the heavy SDK + workspace pkg external (installed alongside).
   external: ['@modelcontextprotocol/sdk', '@tanstack/ai'],
+  // json-schema-to-typescript uses CJS dynamic require(); shims injects
+  // createRequire so those calls work inside this ESM bundle.
+  shims: true,
   banner: { js: '#!/usr/bin/env node' },
 })