tsup.config.ts

import { defineConfig } from "tsup"

/**
 * Heavy optional-peer deps must never be bundled into our dist — the
 * consumer is expected to install them only if they use the corresponding
 * subpath.
 */
const EXTERNAL = [
    "zod",
    "openai",
    "@anthropic-ai/sdk",
    "js-tiktoken",
    "html-to-text",
    "@googlemaps/google-maps-services-js",
    "react",
    "react-dom",
    "react/jsx-runtime",
    "@vis.gl/react-google-maps",
]

/**
 * Single tsup pass that emits every subpath in one go. We previously split
 * the React entry into a separate config block but discovered that tsup's
 * multi-config mode runs stages in parallel, and the core stage's `clean`
 * would race the react stage's output — sometimes wiping the .d.ts files.
 *
 * The `"use client"` directive that Next.js requires at the top of any
 * bundled client module is prepended post-build via the `onSuccess` hook
 * (esbuild silently tree-shakes source-level directives and `banner` options
 * that look like directives, so source-level alternatives are unreliable).
 */
export default defineConfig({
    entry: {
        index: "src/index.ts",
        "utils/index": "src/utils/index.ts",
        "types/index": "src/types/index.ts",
        "scrape/index": "src/scrape/index.ts",
        "search/index": "src/search/index.ts",
        "ai/index": "src/ai/index.ts",
        "geocoding/index": "src/geocoding/index.ts",
        "generate/index": "src/generate/index.ts",
        "react/index": "src/react/index.tsx",
    },
    format: ["esm", "cjs"],
    dts: true,
    sourcemap: true,
    clean: true,
    treeshake: true,
    splitting: false,
    target: "es2022",
    outDir: "dist",
    external: EXTERNAL,
    onSuccess: "node scripts/add-use-client.mjs",
})