🐞 @sanity/export :: stream.on is not a function

[frankleighintercom]

Hey everyone 👋

I'm trying to periodically back up my dataset with the @sanity/export package through a Vercel chron job.

const timestamp = new Date().toISOString();
const filePath = `/tmp/sanity-${timestamp}.tar.gz`;

const client = createClient({
  projectId: process.env.SANITY_STUDIO_PROJECT_ID!,
  dataset: "production",
  apiVersion: "2025-06-11",
  token: process.env.SANITY_STUDIO_READ_API_TOKEN!,
  useCdn: false,
});

await exportDataset({
  client,
  dataset: "production",
  outputPath: filePath,
  assets: true,
  drafts: false,
  raw: false,
});

When i ping this endpoint i get the error stream.on is not a function - What am i doing wrong here?

Discord post

[zafercuz]

I'll just write down what made mine work, I tried asking Claude Code and here's what it suggested to put on my next.config.ts

const nextConfig: NextConfig = {
  /**
   * Exclude Sanity export packages from Next.js bundling
   *
   * PROBLEM:
   * @sanity/export (CommonJS) uses get-it (ESM) for HTTP streaming and archiver for tar.gz creation.
   * When Next.js bundles these packages for server-side execution, it transforms the module system,
   * which breaks native Node.js stream semantics. This causes "stream.on is not a function" errors
   * because the bundled stream objects lose their .on() method.
   *
   * SOLUTION:
   * serverExternalPackages tells Next.js to NOT bundle these packages - they're loaded directly
   * from node_modules at runtime, preserving their native stream functionality.
   *
   * PACKAGES:
   * - @sanity/export: Main export package that orchestrates dataset exports
   * - get-it: HTTP client with native stream support for downloading Sanity data
   * - archiver: Creates tar.gz archives using Node.js streams
   */
  serverExternalPackages: [
    '@sanity/export',
    'get-it',
    'archiver',
  ],
// ...other configurations
}