Practise the standard verbs for configuring the Vite dev server proxy.
0 / 5 completed
1 / 5
Fill in: 'We ___ API requests through Vite's dev server proxy so the frontend and backend can share the same origin locally.'
We 'route requests' — the standard, simple collocation for directing traffic through a configured path. The other options are less idiomatic here.
2 / 5
Fill in: 'Calling the backend on a different port directly from the browser can ___ CORS errors that never happen in production.'
We say a cross-port call will 'cause' CORS errors — the standard collocation for the resulting problem. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the proxy target in vite.config so switching between a local and staging backend takes one line, not a rewrite.'
We 'configure' a target — the standard collocation for setting up a proxy destination. The other options aren't idiomatic here.
4 / 5
Fill in: 'We ___ the path prefix when proxying so /api calls forward correctly without the backend seeing an extra segment.'
We 'rewrite a path' — the standard, established proxy collocation for transforming a request path before forwarding. The other options aren't the recognised term here.
5 / 5
Fill in: 'We ___ WebSocket upgrade support on the proxy config so hot module reload keeps working through the same dev proxy.'
We 'enable' a feature — the standard, simple collocation for turning on proxy WebSocket support. The other options are less idiomatic here.