Incompatible with Next.js App Router due to jsonpath dependency (ENOENT module.js error)

[rubixvi]

The SDK currently breaks in modern Next.js environments (App Router) due to a transitive dependency on jsonpath, which relies on filesystem-based module resolution. This results in runtime errors when the package is bundled.

Error: ENOENT: no such file or directory, open '.../node_modules/jsonpath/include/module.js [middleware] (ecmascript)'

Environment

• Next.js (App Router)
• Node.js runtime (non-edge usage)
• pnpm (strict node_modules structure)
• Payload CMS

import { Dub } from 'dub'

const client = new Dub({ token: process.env.DUB_API_KEY })

Running this in a Next.js project causes the build/runtime to fail with the ENOENT error above.

Workarounds

// next.config.js
serverExternalPackages: ['dub'],

[elie222]

Hitting the same root cause on Next.js 16.2.4 with Turbopack production builds — different surface error though:

Error: EBADF: bad file descriptor, fstat
    at module evaluation (.next/server/chunks/_06tws2d._.js:…)
  errno: -9, code: 'EBADF', syscall: 'fstat'

> Build error occurred
Error: Failed to collect page data for /api/...

Turbopack rewrites require.resolve(...) to a numeric asset id, then fs.readFileSync(<number>) is called at module eval in a worker, which Node treats as an FD and throws EBADF.

The offending code is in jsonpath's lib/grammar.js:

if (fs.readFileSync) {
  grammar.moduleInclude = fs.readFileSync(require.resolve("../include/module.js"));
  grammar.actionInclude = fs.readFileSync(require.resolve("../include/action.js"));
}

Regression point: jsonpath appears as a direct dependency starting in dub@0.71.6. dub@0.71.5 does not pull it in. For anyone blocked, pinning to 0.71.5 is a clean workaround if serverExternalPackages isn't an option (e.g. the import is in a server component / route handler hit during next build's page-data collection).

Would be great to either drop the jsonpath dependency or swap it for something that doesn't do filesystem work at module load.