🐛 Fix: Undefined Variable Reference in Error Handler

[chawdamrunal]

Issue

The error handler in docs/pages/api/sign-cloudinary-params.js references an undefined variable e instead of the correctly scoped error variable, causing a ReferenceError when errors occur.

Bug Details

File: docs/pages/api/sign-cloudinary-params.js:16
Severity: Low
Type: Runtime Error

The catch block defines the error parameter as error, but the code references e.message:

} catch (error) {  // ✅ Parameter named 'error'
  res.status(500).json({
    error: e.message,  // ❌ References 'e' (undefined)
  });
}

Impact

• When signature generation fails, the server throws an additional ReferenceError: e is not defined
• Clients receive incomplete responses or timeouts instead of proper error messages
• The original error is obscured, making debugging difficult

Fix

Changed e.message to error.message to match the catch parameter:

} catch (error) {
  res.status(500).json({
    error: error.message,  // ✅ Correct variable reference
  });
}

Testing

• ✅ Code compiles without errors
• ✅ Variable reference is now consistent
• ✅ Error handler will work correctly when exceptions occur

Hacktoberfest 2025

This contribution is part of Hacktoberfest 2025.

---

Checklist:

• Bug fix for undefined variable
• Simple, focused change
• Clear commit message

[vercel]

Someone is attempting to deploy a commit to the Cloudinary DevX Team on Vercel.

A member of the Team first needs to authorize it.

[eportis-cloudinary]

Thanks so much for catching the issue! Accepting.

[eportis-cloudinary]

@all-contributors please add @chawdamrunal for code

[allcontributors]

@eportis-cloudinary

I've put up a pull request to add @chawdamrunal! 🎉

[github-actions]

🎉 This PR is included in version 6.17.3 🎉

The release is available on:

• pnpm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀