Weird webpack error with nextjs, libsql and pnpm workspaces

Hello there! 👋 I have a side project that uses drizzle with turso in a pnpm workspace with the following structure:

.
├── apps/
│   └── web/
│       └── package.json
├── packages/
│   └── db/
│       └── package.json
├── package.json
└── pnpm-workspaces.yaml

.
├── apps/
│   └── web/
│       └── package.json
├── packages/
│   └── db/
│       └── package.json
├── package.json
└── pnpm-workspaces.yaml

The web app is a Remix app with Vite, and the db package is turso + drizzle, using a db file for local development. Everything works flawlessly and the DX is awesome. Loving Drizzle so far 💖💖💖 The thing is, I wanted a similar setup but with nextjs instead. Webpack hates it and fails to compile with the error shown in the screenshot 🙃 Works fine when moving the db files inside the web app, but then I loose the monorepo structure and I kinda need it for my next project 😅 I've uploaded a minimal repro here https://github.com/carloitaben/nextjs-pnpm-monorepo-libsql-webpack-repro Any ideas? I'm new to monorepos and I'm really curious now 🤔 seems like a funny error. Could it be some ESM/CJS compatibility error? Or something in my tsconfig files? Thanks in advance 🙂

GitHub

GitHub - carloitaben/nextjs-pnpm-monorepo-libsql-webpack-repro

Contribute to carloitaben/nextjs-pnpm-monorepo-libsql-webpack-repro development by creating an account on GitHub.

4 Replies

Angelelz•12mo ago

You might wanna take a look at this page

Angelelz•12mo ago

https://nextjs.org/docs/app/api-reference/next-config-js/transpilePackages

next.config.js Options: transpilePackages | Next.js

Automatically transpile and bundle dependencies from local packages (like monorepos) or from external dependencies (node_modules).

carloOP•12mo ago

Yeah, tried that but doesn't work. I've also tried with the experimental.serverComponentsExternalPackages config but doesn't work either 😅 It's so weird. Installing @libsql/client package in the web app does the trick but it's not ideal, I really want it to just be a dependency of db. Thanks for the help btw 🙌

Angelelz•12mo ago

Install it as a dev dependency while you keep looking. That way there shouldn't be anything in the compiled js Are you sure you're not importing the db somwhere in the front end?

Gaming

Programming

Weird webpack error with nextjs, libsql and pnpm workspaces