nextjs - 💡(How to fix) Fix Turbopack: Dynamic Imports Error when path is not statically analyzable [2 comments, 2 participants]

TL;DR

The issue can be fixed by adjusting the dynamic import statement to work with Turbopack, which may require using a different approach to handle dynamic imports.

Guidance

• Review the Turbopack documentation to understand how it handles dynamic imports, as it may differ from Webpack.
• Consider using next/dynamic with a custom loader function to handle dynamic imports in Turbopack.
• Verify that the atob function is not the cause of the issue by testing with a static string.
• Investigate alternative approaches to generating the sitemap, such as using a separate build step or a library specifically designed for dynamic sitemaps.

Example

// Example of using next/dynamic with a custom loader function
import dynamic from 'next/dynamic';

const Page = dynamic(() => import(`./page`), {
  loader: () => import(`./loader`),
});

Notes

The issue is specific to Turbopack and may require a different solution than what works with Webpack. The use of atob to simulate a dynamic string may be a red herring, and the issue may be related to how Turbopack handles dynamic imports.

Recommendation

Apply a workaround by using a different approach to handle dynamic imports, such as using next/dynamic with a custom loader function. This is because the current implementation is not compatible with Turbopack, and adjusting the import statement or using a different library may be necessary to resolve the issue.