/opt/canhelp/node_modules/next/dist/client/dev
NameSizeModeActions
error-overlay/-0755rm
hot-reloader/-0755rm
amp-dev.d.ts110644editdlrm
amp-dev.js39450644editdlrm
amp-dev.js.map62310644editdlrm
fouc.d.ts570644editdlrm
fouc.js15400644editdlrm
fouc.js.map20540644editdlrm
hot-middleware-client.d.ts3540644editdlrm
hot-middleware-client.js43850644editdlrm
hot-middleware-client.js.map48450644editdlrm
noop-turbopack-hmr.d.ts410644editdlrm
noop-turbopack-hmr.js7420644editdlrm
noop-turbopack-hmr.js.map3860644editdlrm
on-demand-entries-client.d.ts830644editdlrm
on-demand-entries-client.js21440644editdlrm
on-demand-entries-client.js.map21420644editdlrm
report-hmr-latency.d.ts8610644editdlrm
report-hmr-latency.js19770644editdlrm
report-hmr-latency.js.map25370644editdlrm
runtime-error-handler.d.ts770644editdlrm
runtime-error-handler.js6610644editdlrm
runtime-error-handler.js.map3050644editdlrm
Edit: /opt/canhelp/node_modules/next/dist/client/dev/report-hmr-latency.d.ts (861B)
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, startMsSinceEpoch: number, endMsSinceEpoch: number, hasUpdate?: boolean): void;