nextjs - 💡(How to fix) Fix `compiler.define` config should support booleans [1 participants]

TL;DR

The warning can be resolved by changing the type of __DEV__ in next.config.mjs to a string.

Guidance

• Verify that the issue is caused by the __DEV__ value being a boolean instead of a string by checking the next.config.mjs file.
• Update the next.config.mjs file to use a string value for __DEV__, for example:

compiler: {
  define: {
    __DEV__: 'true'
  }
}

• Run next build again to check if the warning is resolved.
• If the issue persists, check the Next.js documentation for any specific requirements for the compiler.define options.

Notes

This solution assumes that the warning is caused by the type mismatch and that changing the type to a string will resolve the issue. If the issue is more complex, additional debugging may be required.

Recommendation

Apply workaround: changing the type of __DEV__ to a string, as this is a simple and non-invasive fix that is likely to resolve the warning.