Vercel Serverless Cannot find module '@libsql/linux-x64-gnu'

TL;DR

Fix: Next.js/Vercel: use the documented extra bundler config for Next.js ('Using the library with Next.js' in the README; not needed on newer Next with vercel/next.js#(55266) - 0.3.5-pre.2 resolved it for the reporter on both Vercel runtimes.

The error

Issue tursodatabase/libsql-client-ts#84 (closed, 7 comments): After upgrading to @libsql/client@0.3.3-pre.2 it started giving me this error in the Vercel logs --- @libsql/client@0.3.2 works fine.

Fix

1. Next.js/Vercel: use the documented extra bundler config for Next.js ('Using the library with Next.js' in the README; not needed on newer Next with vercel/next.js#(55266) - 0.3.5-pre.2 resolved it for the reporter on both Vercel runtimes.

Success check: the symptom above is gone and the original operation completes.

When to use

• You hit this exact symptom in libsql-client-ts.
• You want the verified fix without digging through the thread.

When not to use

• A different error in libsql-client-ts, even a similar-looking one.
• General libsql-client-ts setup or credential questions.

Compatibility

• Libsql Client Ts (tursodatabase/libsql-client-ts)

Variant phrasings

• How to fix "vercel Serverless Cannot find module '@libsql/linux-x64-gnu'" in libsql-client-ts
• libsql-client-ts: vercel Serverless Cannot find module '@libsql/linux-x64-gnu'

Edge cases

• AWS Lambda / other serverless: import @libsql/client/web instead - same API without the optional native dependency, so no @libsql/linux-x64-gnu module is ever required.

Source

• https://github.com/tursodatabase/libsql-client-ts/issues/84

Asked in gh:tursodatabase/libsql-client-ts#84 (https://github.com/tursodatabase/libsql-client-ts/issues/84): Vercel Serverless Cannot find module '@libsql/linux-x64-gnu'. The issue report: Issue tursodatabase/libsql-client-ts#84 (closed, 7 comments): After upgrading to @libsql/client@0.3.3-pre.2 it started giving me this error in the Vercel logs --- @libsql/client@0.3.2 works fine.

Require stack:
- /var/task/node_modules/.pnpm/libsql@0.1.4/node_modules/libsql/index.js
- /var/task/node_modules/.pnpm/@libsql+client@0.3.3-pre.2/node_modules/@libsql/client/lib-cjs/sqlite3.js
- /var/task/node_modules/.pnpm/@libsql+client@0.3.3-pre.2/node_modules/@libsql/client/lib-cjs/node.js
- /var/task/node_modules/.pnpm/drizzle-orm@0.28.6_@libsql+client@0.3.3-pre.2/node_modules/drizzle-orm/libsql/index.cj The verified answer: [penberg (maintainer)]: Two fixes depending on environment. Next.js/Vercel: use the documented extra bundler config for Next.js ('Using the library with Next.js' in the README; not needed on newer Next with vercel/next.js#55266)  -  0.3.5-pre.2 resolved it for the reporter on both Vercel runtimes. AWS Lambda / other serverless: import `@libsql/client/web` instead  -  same API without the optional native dependency, so no `@libsql/linux-x64-gnu` module is ever required.