17ae928331
overhaul the collection pool page's ready status UI: split the clickable chip into a static status indicator and dedicated toggle button with loading state, improving user clarity between status and actionable elements update all related copy (toast messages, filter labels, button text) to use consistent "awaiting supplier confirmation" terminology across the interface remove invalid `transparent` prop from traffic tile layers in both the collection map and traffic tiles components, update comments to reflect Leaflet does not support this option add wildcard to allowedDevOrigins in next.config.ts to simplify local development testing across different network interfaces add a comprehensive database backfill script to fix assigned order items missing the `ready_for_collection` flag, ensuring drivers see their correct assigned stops in the driver app
12 lines
499 B
TypeScript
12 lines
499 B
TypeScript
import type { NextConfig } from "next";
|
|
|
|
const nextConfig: NextConfig = {
|
|
output: "standalone",
|
|
// Dev server blocks cross-origin HMR requests by default in Next 16. The
|
|
// app is normally loaded on `localhost`, but we also load it on
|
|
// `127.0.0.1` (and on the LAN IP for phone testing). Listing both keeps
|
|
// the HMR client from hanging on the first load.
|
|
allowedDevOrigins: ["127.0.0.1", "localhost", "192.168.1.122", "192.168.1.128", "*"],
|
|
};
|
|
|
|
export default nextConfig;
|