Potential fix for code scanning alert no. 45: Information exposure through a stack trace

[Tanker187]

Potential fix for https://github.com/Tanker187/vite/security/code-scanning/45

In general, the fix is to stop sending the stack trace back to the client and instead send a generic error message while logging the detailed error on the server. The server log can still include e.stack so that developers can debug issues without exposing internal details to users.

For this specific file, the best minimal fix that preserves existing behavior is:

• Keep logging e.stack to the server console (or otherwise), so debugging remains possible.
• Change res.status(500).end(e.stack) to return a generic message that does not contain the stack trace or internal details, for example "Internal Server Error" or a similar neutral string.
• Optionally, you may choose a different message depending on environment (e.g., slightly more descriptive in non‑prod), but it should never include e.stack.

Concretely, in playground/ssr-conditions/server.js within the catch (e) block around line 69:

• Leave vite && vite.ssrFixStacktrace(e) and console.log(e.stack) as-is.
• Replace res.status(500).end(e.stack) with a call that sends a fixed message such as res.status(500).end('Internal Server Error').

No additional imports or helper methods are needed; Express already supports this usage.

---

Suggested fixes powered by Copilot Autofix. Review carefully before merging.