nextjs - 💡(How to fix) Fix Using serverExternalPackages for monorepo workspaces does not work [1 participants]

TL;DR

• Review and adjust the serverExternalPackages configuration in next.config.ts to ensure correct exclusion of workspace packages like @my-project/common from the server bundle.

Guidance

• Verify that the serverExternalPackages option is correctly set to exclude @my-project/common and other unwanted workspaces from being bundled into the server code.
• Check the Next.js documentation for the correct syntax and usage of serverExternalPackages to ensure it matches the expected behavior.
• Inspect the next.config.ts file for any potential overrides or custom configurations that might be causing the incorrect bundling.
• Test the build process with a minimal setup to isolate if the issue is specific to the @my-project/common package or a more general configuration problem.

Example

No specific code example is provided due to the lack of direct code references in the issue, but reviewing the next.config.ts file for something like:

module.exports = {
  //... other configurations ...
  serverExternalPackages: ['@my-project/common'],
}

could be a starting point for adjustments.

Notes

The solution may depend on the specific version of Next.js being used, as indicated by differences in behavior between older and newer versions mentioned in the issue.

Recommendation

• Apply workaround: Adjust the serverExternalPackages configuration as needed to correctly exclude unwanted packages from the server bundle, as the issue seems related to a misconfiguration rather than a version-specific bug that could be fixed by upgrading.