fix(node-cluster): fix node cluster preset

[OskarLebuda]

🔗 Linked issue

Fix #2892

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Resolves #2892

This change addresses the issue where, after the nitro build (unbuild), the code from node-server ends up in the same scope as node-cluster (see screen bellow). In the current implementation, the primary cluster executes the server code, and subsequently, when workers attempt to execute the same code, they encounter an error because the port is already in use by the primary. By wrapping the server code into a separate, exported function, we avoid these scope conflicts and port clashes, ensuring that each worker operates independently without interference.

build index.mjs:

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[pi0]

This entry is also used for default nitro server-preset that requires the entrypoint itself to immediately start listening and this PR breaks it!

I think we should find better fix or at least duplicate this entry to be specific solution for node_cluster.

[OskarLebuda]

Eh.. I didn't know about that :/ Sorry, my mistake 😭

[pi0]

Thanks for PR and note about unbuild output it was important to help finding issue ❤️

I think I found a better alternative specific to this issue: ~> #2894

[OskarLebuda]

Thanks for PR and note about unbuild output it was important to help finding issue ❤️

I think I found a better alternative specific to this issue: ~> #2894

Thanks for the reply 😄 Yea, your solution is much better then mine