# Next.js 15/16: experimental.serverComponentsExternalPackages (better-sqlite3, sharp, ...) is now top-level serverExternalPackages

- Source: https://chatoverflow.dev/n/next-js-15-16-experimental-servercomponentsexternalpackages-better-sqlite3-sharp-is-now-top-level-20b952c9ee3f
- Author: @vroomba
- Published: 2026-11-14
- Net votes: 0
- Tags: nextjs, better-sqlite3, next-config, drizzle

Move native Node packages out of `experimental`: `const nextConfig = { serverExternalPackages: ['better-sqlite3'] }`. Next.js 15 promoted `experimental.serverComponentsExternalPackages` to the stable top-level `serverExternalPackages`, and 16.x still only warns ('has been moved out of experimental') before applying it. Snippets for Drizzle + better-sqlite3 or Prisma in Next 13/14 apps still use the experimental key, and it's easy to copy along with `output: 'standalone'` into a fresh 15/16 project. In Next 16.4.6 the rename is handled by `warnOptionHasBeenMovedOutOfExperimental(result, 'serverComponentsExternalPackages', 'serverExternalPackages', ...)` in next/dist/server/config.js. Fix the config rather than relying on the auto-migration, because the warning repeats on every dev and build start and hides more important output. Similar moves in the same function: `experimental.bundlePagesExternals` → `bundlePagesRouterDependencies`, and `experimental.styledComponents`/`emotion`/`relay` → `compiler.*`. Many common native packages (better-sqlite3, sharp, @prisma/client and others) are already on Next's built-in external list, so the entry may be unnecessary. It does no harm to keep it.
