summaryrefslogtreecommitdiff
path: root/frontend-old/node_modules/web-vitals/dist/modules/attribution/onTTFB.d.ts
diff options
context:
space:
mode:
Diffstat (limited to 'frontend-old/node_modules/web-vitals/dist/modules/attribution/onTTFB.d.ts')
-rw-r--r--frontend-old/node_modules/web-vitals/dist/modules/attribution/onTTFB.d.ts17
1 files changed, 17 insertions, 0 deletions
diff --git a/frontend-old/node_modules/web-vitals/dist/modules/attribution/onTTFB.d.ts b/frontend-old/node_modules/web-vitals/dist/modules/attribution/onTTFB.d.ts
new file mode 100644
index 0000000..a39d0ad
--- /dev/null
+++ b/frontend-old/node_modules/web-vitals/dist/modules/attribution/onTTFB.d.ts
@@ -0,0 +1,17 @@
+import { TTFBMetricWithAttribution, ReportOpts } from '../types.js';
+/**
+ * Calculates the [TTFB](https://web.dev/articles/ttfb) value for the
+ * current page and calls the `callback` function once the page has loaded,
+ * along with the relevant `navigation` performance entry used to determine the
+ * value. The reported value is a `DOMHighResTimeStamp`.
+ *
+ * Note, this function waits until after the page is loaded to call `callback`
+ * in order to ensure all properties of the `navigation` entry are populated.
+ * This is useful if you want to report on other metrics exposed by the
+ * [Navigation Timing API](https://w3c.github.io/navigation-timing/). For
+ * example, the TTFB metric starts from the page's [time
+ * origin](https://www.w3.org/TR/hr-time-2/#sec-time-origin), which means it
+ * includes time spent on DNS lookup, connection negotiation, network latency,
+ * and server processing time.
+ */
+export declare const onTTFB: (onReport: (metric: TTFBMetricWithAttribution) => void, opts?: ReportOpts) => void;