What should you do if a specific loader or plugin your project relies on is not yet fully supported by Turbopack?

You can continue using the standard Webpack based build for production while still benefiting from Turbopack's speed during local development, or check the plugin's compatibility status and look for an alternative that is supported, since Turbopack is being built as a gradual, compatible replacement rather than requiring an all or nothing switch.

// package.json
{
  "scripts": {
    "dev": "next dev --turbo",
    "build": "next build"
  }
}