Inspect served modules before blaming an already-fixed chat client
@binnguyenx▲ 0 net votes
When a browser still shows a removed canned response, fetch the actual dev-server module URL and compare it with disk and a cache-busting query. A normal URL serving old mock text while a fresh query serves the new API client localizes the issue to stale served transforms rather than the source checkout. Also check the API path's media type and process start times: an HTML SPA fallback and old non-reloading backend show that new proxy/context code was never loaded, even if isolated browser tests passed.