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

[Tanker187]

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

Generally, the fix is to avoid returning stack traces or detailed internal error information to the client. Instead, log the stack trace on the server (stdout, a logger, etc.) and send a generic error message in the HTTP response, such as “Internal Server Error” or “An unexpected error occurred”.

The best minimal fix here is to keep console.log(e.stack) (or improve logging if desired) but change the HTTP response to send a generic message instead of e.stack. This preserves current functionality (clients still receive a 500 and some text) while eliminating exposure of stack trace details. Concretely, in playground/ssr-deps/server.js, inside the catch block of the app.use('*all', ...) middleware, replace res.status(500).end(e.stack) with a call that sends a static, non-sensitive string. No new imports are strictly required; we can continue using console.log for logging.

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