duckdb-wasm: ok under pages/, broken under app/

[ryan-williams]

duckdb-wasm can load a Parquet file on the server in a pages/ page (demo), but not in a similar app/ page.

Full repro/details at ryan-williams/next-duckdb-parquet-demo:

⚠️ Broken under "App Router" ⚠️

For some reason, the server-side loadParquet path doesn't seem to work under Next.js's new "App router."

Here's a trimmed down example (from the @app-broken branch):

• pages/pages.tsx ✅ works
• app/app/page.tsx ❌ broken

Attempting to load the latter emits this on the server side:

duckdb-wasm fetch
bestBundle: {
  mainModule: '/Users/ryan/c/next-duckdb-parquet-demo/node_modules/@duckdb/duckdb-wasm/dist/duckdb-eh.wasm',
  mainWorker: '/Users/ryan/c/next-duckdb-parquet-demo/node_modules/@duckdb/duckdb-wasm/dist/duckdb-node-eh.worker.cjs',
  pthreadWorker: null
}
made logger
made db
worker terminated with 1 pending requests

and the client hangs.

Similarly, next build times out, meaning I can't deploy a demo. Here's a GitHub Actions run that failed due to this issue.

diff pages/pages.tsx app/app/page.tsx:

-export async function getStaticProps() {
-    const data = await loadParquet<Person>(parquetPath)  // ✅ works fine under pages/
-    return { props: { data } }
-}
-
-export default function Home({ data }: { data: Person[] }) {
+export default async function Home() {
+    const data = await loadParquet<Person>(parquetPath)  // ❌ broken under app/

This line:

await db.instantiate(bundle.mainModule, bundle.pthreadWorker);

emits this error:

worker terminated with 1 pending requests

I haven't found any further leads about what might be going on.

[ryan-williams]

I documented some more instances of the worker terminated with 1 pending requests issue at duckdb/duckdb-wasm#1588.

[michaelwallabi]

Ran into this issue today as well within an /api route, always hangs on instantiate with the same messages you post.

[michaelwallabi]

Similar to @ryan-williams, I got here after discovering that using duckdb-node doesn't seem to work in Vercel due to lambda issues.

duckdb/duckdb-node#15