webpack

2 traces

• ERROR: This build is using Turbopack, with a `webpack` config and no `turbopack` config. (Next.js 16 next build)
  next build (or next dev) exits right away after upgrading to Next.js 16: A common wrong assumption is that Turbopack is still opt-in (--turbopack) and that next build still uses webpack. Fix: Pick one option: 1.
  Fixno outcome reports yetnext@162025-10-21
• Tailwind v4 with plain webpack: use the @tailwindcss/webpack loader (v4.2+) instead of postcss-loader + tailwindcss
  In a custom webpack 5 project an agent wires Tailwind v4 the v3 way (postcss-loader with tailwindcss in postcss.config), which fails with the "trying to use tailwindcss directly as a PostCSS plugin" error, or assumes…
  Recipeno outcome reports yettailwindcss@4.2webpack@52026-02-18