Turbopack does not yet support this feature

What causes this

Turbopack is Next.js’s Rust-based bundler that replaces Webpack. It’s significantly faster but doesn’t support every Webpack feature yet. When you use next dev --turbo and your project uses an unsupported feature, you get this error.

Common unsupported features:

• Custom Webpack loaders (e.g., svg-loader, raw-loader)
• Certain next.config.js webpack configuration options
• Some CSS preprocessor configurations
• Specific module federation setups
• Custom Webpack plugins

Fix 1: Fall back to Webpack

The quickest fix — just don’t use Turbopack:

# ❌ With Turbopack
next dev --turbo

# ✅ Without Turbopack (uses Webpack)
next dev

Update your package.json scripts if needed:

{
  "scripts": {
    "dev": "next dev"
  }
}

Fix 2: Replace the unsupported feature

Often there’s a Turbopack-compatible alternative:

// next.config.js

// ❌ Custom Webpack loader — not supported in Turbopack
module.exports = {
  webpack: (config) => {
    config.module.rules.push({
      test: /\.svg$/,
      use: ['@svgr/webpack'],
    });
    return config;
  },
};

// ✅ Use @svgr/next which supports Turbopack
const withSvgr = require('@svgr/next');
module.exports = withSvgr({
  // your config
});

Fix 3: Check the compatibility list

Turbopack’s feature support is actively expanding. Check the current status:

# Check your Next.js version — newer versions support more features
npx next --version

The Next.js docs maintain an up-to-date compatibility table. Your feature might be supported in a newer version:

npm install next@latest

Fix 4: Use Turbopack conditionally

Use Turbopack in development (where speed matters most) and Webpack in production:

{
  "scripts": {
    "dev": "next dev --turbo",
    "build": "next build"
  }
}

If Turbopack fails in dev, fall back:

{
  "scripts": {
    "dev": "next dev",
    "dev:turbo": "next dev --turbo",
    "build": "next build"
  }
}

Related resources

• Next.js cheat sheet
• Next.js complete guide

How to prevent it

• Check Turbopack compatibility before adding custom Webpack config to a Next.js project
• Prefer Next.js built-in features (Image, Font, CSS Modules) over custom Webpack loaders — they work with both bundlers
• Keep Next.js updated — each release adds more Turbopack support
• If you need custom Webpack config, accept that you’ll use Webpack for now and revisit Turbopack later

Related: What is Next.js