From 8eff962cab608341a6f2fedc640a0e32d96f26e2 Mon Sep 17 00:00:00 2001 From: altaf-creator Date: Sun, 9 Nov 2025 11:15:19 +0800 Subject: pain --- .../web-vitals/dist/modules/onINP.d.ts | 31 ++++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 frontend-old/node_modules/web-vitals/dist/modules/onINP.d.ts (limited to 'frontend-old/node_modules/web-vitals/dist/modules/onINP.d.ts') diff --git a/frontend-old/node_modules/web-vitals/dist/modules/onINP.d.ts b/frontend-old/node_modules/web-vitals/dist/modules/onINP.d.ts new file mode 100644 index 0000000..50c3e33 --- /dev/null +++ b/frontend-old/node_modules/web-vitals/dist/modules/onINP.d.ts @@ -0,0 +1,31 @@ +import { INPMetric, MetricRatingThresholds, ReportOpts } from './types.js'; +/** Thresholds for INP. See https://web.dev/articles/inp#what_is_a_good_inp_score */ +export declare const INPThresholds: MetricRatingThresholds; +/** + * Calculates the [INP](https://web.dev/articles/inp) value for the current + * page and calls the `callback` function once the value is ready, along with + * the `event` performance entries reported for that interaction. The reported + * value is a `DOMHighResTimeStamp`. + * + * A custom `durationThreshold` configuration option can optionally be passed to + * control what `event-timing` entries are considered for INP reporting. The + * default threshold is `40`, which means INP scores of less than 40 are + * reported as 0. Note that this will not affect your 75th percentile INP value + * unless that value is also less than 40 (well below the recommended + * [good](https://web.dev/articles/inp#what_is_a_good_inp_score) threshold). + * + * If the `reportAllChanges` configuration option is set to `true`, the + * `callback` function will be called as soon as the value is initially + * determined as well as any time the value changes throughout the page + * lifespan. + * + * _**Important:** INP should be continually monitored for changes throughout + * the entire lifespan of a page—including if the user returns to the page after + * it's been hidden/backgrounded. However, since browsers often [will not fire + * additional callbacks once the user has backgrounded a + * page](https://developer.chrome.com/blog/page-lifecycle-api/#advice-hidden), + * `callback` is always called when the page's visibility state changes to + * hidden. As a result, the `callback` function might be called multiple times + * during the same page load._ + */ +export declare const onINP: (onReport: (metric: INPMetric) => void, opts?: ReportOpts) => void; -- cgit v1.2.3