fix: Improved Error Handling, Logging, and Code Readability in Build …

[annwag]

I’ve made several key improvements to the build process to ensure better error handling, logging, and overall code clarity:

1. Error Handling in build.onEnd:

   • Previously, errors were logged but didn’t exit with an error code.
   • Now, process.exit(1) ensures the build process fails explicitly when errors occur, which is critical for CI/CD pipelines and automation.

2. Error Logging in build():

   • Errors were caught but not logged, making debugging difficult.
   • Added console.error('❌ Build failed:', error) to provide clear visibility into what went wrong.

3. Simplified Promise.all:

   • Removed unnecessary Promise.all for a single context, directly awaiting esbuild.context instead.
   • This improves code readability and reduces complexity.

4. Added Comments for Clarity:

   • Included detailed comments to explain the purpose of each section, making the code easier to understand and maintain.

[vercel]

@annwag is attempting to deploy a commit to the rainbowdotme Team on Vercel.

A member of the Team first needs to authorize it.