nextjs - 💡(How to fix) Fix Module not found: Can't resolve './libsodium.mjs' with Turbopack [1 comments, 2 participants]

TL;DR

The most likely fix is to disable Turbopack by running next dev instead of next dev --turbopack to resolve the module resolution error with libsodium-wrappers.

Guidance

• Verify that the issue is specific to Turbopack by comparing the behavior with and without Turbopack enabled.
• Check the libsodium-wrappers documentation for any known issues or workarounds related to Turbopack compatibility.
• Consider reporting the issue to the libsodium-wrappers or Next.js teams to investigate potential fixes or improvements for Turbopack support.
• As a temporary workaround, use the standard webpack bundler by running next dev instead of next dev --turbopack to ensure the application runs correctly.

Example

No code snippet is provided as the issue is related to module resolution and build configuration rather than code-specific logic.

Notes

The issue seems to be related to Turbopack's handling of dynamic imports and WASM files used by libsodium-wrappers. Disabling Turbopack resolves the issue, but a more permanent solution may require updates to libsodium-wrappers or Next.js to improve Turbopack compatibility.

Recommendation

Apply the workaround by running next dev instead of next dev --turbopack, as it allows the application to run correctly while waiting for potential fixes or improvements in libsodium-wrappers or Next.js.