nextjs - 💡(How to fix) Fix Azure Maps Incompatible with Turbopack [1 participants]

TL;DR

• The most likely fix involves configuring Turbopack to properly handle the azure-maps-control package, potentially by adding it to a list of packages that require special handling or transpilation.

Guidance

• Investigate Turbopack configuration options to see if there's a way to specify packages that need transpilation or special handling, similar to how it was done with Babel and Webpack.
• Review the Next.js documentation and Turbopack documentation for any mentions of handling third-party packages like azure-maps-control.
• Consider reaching out to the Next.js or Turbopack community for guidance on how to handle this specific package, as it may be a known issue.
• If possible, try to reproduce the issue with a minimal example to isolate the problem and make it easier to debug.

Example

No specific code example can be provided without more information on the Turbopack configuration options.

Notes

• The provided workaround using Babel and Webpack suggests that the issue is related to how the azure-maps-control package is being handled, but it's not ideal due to the potential deprecation of Webpack.
• Without more information on the Turbopack configuration options, it's difficult to provide a more specific solution.

Recommendation

• Apply workaround: Using Babel, Webpack, and adding the azure-maps-control package to the transpiled packages section in the config, as it has been shown to work, even if it's not the ideal long-term solution. This allows for continued functionality while a more permanent solution using Turbopack is explored.