nextjs - 💡(How to fix) Fix When Turbopack is enabled, generateBuildId executes on next dev [1 comments, 2 participants]

You should see the following error thrown This remains true if you build with webpack via next dev --webpack. When webpack is enabled, the error that I added to the repo to reproduce the error will not be thrown.

TL;DR

The issue can be resolved by ensuring that the generateBuildId function is properly configured to handle the next dev command with Turbopack.

Guidance

• Review the next.config.js file to ensure that the generateBuildId function is correctly implemented and handles the next dev command.
• Verify that the REVISION environment variable is set when running next dev with Turbopack.
• Check the Next.js documentation for any specific requirements or recommendations for using generateBuildId with Turbopack.
• Consider adding a conditional statement to the generateBuildId function to handle the difference in behavior between next build and next dev.

Example

// next.config.js
module.exports = {
  // ...
  generateBuildId: async () => {
    if (process.env.NODE_ENV === 'development') {
      // Handle next dev with Turbopack
      return 'development-build-id';
    }
    // Handle next build
    return 'production-build-id';
  },
};

Notes

The issue seems to be related to the change in behavior when using Turbopack with next dev. The generateBuildId function is not properly handling this scenario, resulting in the error.

Recommendation

Apply workaround: Modify the generateBuildId function to handle the next dev command with Turbopack, as shown in the example above. This will allow the application to run without errors when using Turbopack with next dev.