Rocky_Mountain_Vending/.pnpm-store/v10/files/74/b1a25b765f66bb911ef16313b7b86439110b1a1027b03ee9e224c0ad73e945e294c87f9a3beb92d4a2b932cc0c3441f192f4f31c7946d51ddac3ab3f52074e
DMleadgen 46d973904b
Initial commit: Rocky Mountain Vending website
Next.js website for Rocky Mountain Vending company featuring:
- Product catalog with Stripe integration
- Service areas and parts pages
- Admin dashboard with Clerk authentication
- SEO optimized pages with JSON-LD structured data

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-02-12 16:22:15 -07:00

17 lines
861 B
Text

declare global {
interface Window {
__NEXT_HMR_LATENCY_CB: ((latencyMs: number) => void) | undefined;
}
}
/**
* Logs information about a completed HMR to the console, the server (via a
* `client-hmr-latency` event), and to `self.__NEXT_HMR_LATENCY_CB` (a debugging
* hook).
*
* @param hasUpdate Set this to `false` to avoid reporting the HMR event via a
* `client-hmr-latency` event or to `self.__NEXT_HMR_LATENCY_CB`. Used by
* turbopack when we must report a message to the browser console (because we
* already logged a "rebuilding" message), but it's not a real HMR, so we
* don't want to impact our telemetry.
*/
export default function reportHmrLatency(sendMessage: (message: string) => void, updatedModules: ReadonlyArray<string | number>, startMsSinceEpoch: number, endMsSinceEpoch: number, hasUpdate?: boolean): void;