Find the bug before you fix it

What the error means. Cannot read properties of undefined (reading 'map') means orders was undefined at the moment the component rendered. The array never arrived, or it arrived under a different name.

Most likely causes

1. The first render happens before the data loads. Your useEffect fetch is asynchronous, and useState() has no initial value, so orders is undefined on the first pass. The stack trace points at line 14, which is the first render.
2. The API shape changed. You mentioned this started after the backend deploy. If the response went from [...] to { data: [...] }, then setOrders(json) stores an object and .map fails. That would be a different message though ("map is not a function"), so this is less likely.
3. The request fails and the error is swallowed. There is no catch, so a 401 would leave orders untouched.

Quick check

Add console.log("orders:", orders) on the line above the return. If the first log says undefined and the second shows an array, it is cause 1.

The fix

const [orders, setOrders] = useState([]);
const [status, setStatus] = useState("loading");

Then render a loading state while status === "loading" and an error state if the fetch fails. This fixes the cause because the component now has a valid value for every moment in its life, instead of assuming the data is already there.

Avoid orders?.map(...) on its own. It hides the crash, but the user would stare at an empty page with no idea why.

Catching it earlier

With TypeScript, useState<Order[]>() without an initial value has the type Order[] | undefined, and the compiler refuses the .map call until you handle it.