FM / dev

/opt/canhelp/node_modules/next/dist/esm/client/dev/

/opt/canhelp/node_modules/next/dist/esm/client/dev

Name	Size	Mode	Actions
error-overlay/	-	0755	rm
hot-reloader/	-	0755	rm
amp-dev.js	3294	0644	edit dl rm
amp-dev.js.map	6286	0644	edit dl rm
fouc.js	1228	0644	edit dl rm
fouc.js.map	2076	0644	edit dl rm
hot-middleware-client.js	3644	0644	edit dl rm
hot-middleware-client.js.map	4825	0644	edit dl rm
noop-turbopack-hmr.js	222	0644	edit dl rm
noop-turbopack-hmr.js.map	370	0644	edit dl rm
on-demand-entries-client.js	1415	0644	edit dl rm
on-demand-entries-client.js.map	2130	0644	edit dl rm
report-hmr-latency.js	1456	0644	edit dl rm
report-hmr-latency.js.map	2521	0644	edit dl rm
runtime-error-handler.js	117	0644	edit dl rm
runtime-error-handler.js.map	294	0644	edit dl rm

Edit: /opt/canhelp/node_modules/next/dist/esm/client/dev/report-hmr-latency.js (1456B)

/**
 * 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, updatedModules, startMsSinceEpoch, endMsSinceEpoch, hasUpdate) {
    if (hasUpdate === void 0) hasUpdate = true;
    const latencyMs = endMsSinceEpoch - startMsSinceEpoch;
    console.log("[Fast Refresh] done in " + latencyMs + "ms");
    if (!hasUpdate) {
        return;
    }
    sendMessage(JSON.stringify({
        event: 'client-hmr-latency',
        id: window.__nextDevClientId,
        startTime: startMsSinceEpoch,
        endTime: endMsSinceEpoch,
        page: window.location.pathname,
        updatedModules,
        // Whether the page (tab) was hidden at the time the event occurred.
        // This can impact the accuracy of the event's timing.
        isPageHidden: document.visibilityState === 'hidden'
    }));
    if (self.__NEXT_HMR_LATENCY_CB) {
        self.__NEXT_HMR_LATENCY_CB(latencyMs);
    }
}

//# sourceMappingURL=report-hmr-latency.js.map

/** * 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, updatedModules, startMsSinceEpoch, endMsSinceEpoch, hasUpdate) { if (hasUpdate === void 0) hasUpdate = true; const latencyMs = endMsSinceEpoch - startMsSinceEpoch; console.log("[Fast Refresh] done in " + latencyMs + "ms"); if (!hasUpdate) { return; } sendMessage(JSON.stringify({ event: 'client-hmr-latency', id: window.__nextDevClientId, startTime: startMsSinceEpoch, endTime: endMsSinceEpoch, page: window.location.pathname, updatedModules, // Whether the page (tab) was hidden at the time the event occurred. // This can impact the accuracy of the event's timing. isPageHidden: document.visibilityState === 'hidden' })); if (self.__NEXT_HMR_LATENCY_CB) { self.__NEXT_HMR_LATENCY_CB(latencyMs); } } //# sourceMappingURL=report-hmr-latency.js.map