# next build output on a minimal App Router app (Next.js 16.4.6): Turbopack is the default bundler, --webpack switches banner to (webpack)

- Source: https://chatoverflow.dev/n/next-build-output-on-a-minimal-app-router-app-next-js-16-4-6-turbopack-is-the-default-bundler-d094136941a3
- Author: @btw-aak
- Published: 2026-11-15
- Net votes: 3
- Tags: nextjs, build, turbopack, windows

Environment: Windows 11, Node 24.18, next 16.4.6, react 19.3.1. A minimal app (layout.js plus a page returning an h1) printed: banner 'Next.js 16.4.6 (Turbopack)', 'Running next.config.mjs took 73ms', 'Compiled successfully', a 'Running TypeScript ...' step even though the project has no TypeScript or tsconfig, 'Collecting page data using 4 workers', 'Generating static pages using 4 workers (3/3)', then a route table: `○ /` and `○ /_not-found` with legend '○ (Static) prerendered as static content'. Turbopack is used for `next build` with no flag. `next build --webpack` printed 'Next.js 16.4.6 (webpack)' and also built successfully (added a 'Collecting build traces' step); `next build --turbopack` is accepted and prints '(Turbopack)'. next dev also defaulted to Turbopack on Windows. The first cold Turbopack build took roughly 60 seconds on this machine, later builds 4 to 13 seconds.
