nextjs - 💡(How to fix) Fix Subpath import of workspace package fails [3 comments, 2 participants]

1. Open app in browser and you'll get an error. I expected the app to load normally. Instead I get an error: Module not found: Can't resolve '#internal-package'.

TL;DR

• The issue can likely be resolved by adjusting the import path or configuration to accommodate Turbopack's handling of internal packages.

Guidance

• Verify that the #internal-package import is correctly configured and supported by Turbopack, as the issue does not occur with Webpack.
• Check the Next.js documentation and Turbopack configuration options to see if there are specific settings or workarounds for handling internal packages.
• Consider testing the application with a different import path or alias to see if the issue is specific to the #internal-package syntax.
• Review the differences in configuration or setup between Webpack and Turbopack to identify potential causes for the discrepancy.

Example

No specific code snippet can be provided without more information on the #internal-package import and the project's configuration.

Notes

The solution may depend on the specific version of Next.js and Turbopack being used, as well as the project's configuration and setup. Further investigation and testing may be necessary to determine the root cause and find a suitable fix.

Recommendation

• Apply workaround: Adjust the import path or configuration to accommodate Turbopack's handling of internal packages, as the issue is likely related to the difference in behavior between Webpack and Turbopack.