Potential fix for code scanning alert no. 6: Missing rate limiting

[Tanker187]

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

In general, to fix missing rate limiting in an Express route that performs expensive operations, you add a rate-limiting middleware (for example, from express-rate-limit) and apply it before the expensive handler, either globally (app.use(limiter)) or to specific routes.

For this specific file, the simplest fix without changing existing behavior is:

• Import express-rate-limit using ES module syntax.
• Define a limiter instance with a reasonable window and request cap.
• Apply this limiter as middleware to the '*all' route so that the expensive handler is protected, while leaving the rest of the Vite middleware stack untouched.

Concretely:

• At the top of playground/optimize-missing-deps/server.js, add import rateLimit from 'express-rate-limit'.
• After creating const app = express(), define const limiter = rateLimit({ windowMs: 15 * 60 * 1000, max: 100 }) (or similar).
• Change app.use('*all', async (req, res) => { ... }) to app.use('*all', limiter, async (req, res) => { ... }), preserving the existing handler body.

No other logic in the handler needs to change.

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