Event not being fired or fired with no value about web-vitals HOT 4 CLOSED

I'm not familiar with how reporting in New Relic works, but is it possible that the expression window.newrelic.setCustomAttribute(event, value); is running after your New Relic JS code is sending data to its servers? That would certainly explain why you're not seeing values in some cases. (E.g. if New Relic is sending data in the load event, but first input happens after load.)

But I realized that a few times the events are not being fired at all or with no value attached.

Can you get me an example of what you mean by "no value attached"? Do you mean a value of zero? Do you mean a value of null / undefined, do you mean the value property does not exist on the reported object?

The way the library is built, it might be possible that a zero value is reported (this is common in the case of CLS), but a null, undefined or non-existent value should never be reported.

The Google Chrome extension shows really different numbers for the same page.

Again, can you give me an example? And are you talking about a difference in the number being reported to New Relic or the numbers be logged to the console by the web-vitals library? If it's the numbers being reported to New Relic then I suspect it's an issue with how you're using their library (see my first paragraph).

from web-vitals.

The first item was already fixed! thanks!
Now about the Google Chrome extension, if you load any page at different times you will get quite a few different results.

from web-vitals.

The first item was already fixed! thanks!

Great!

Now about the Google Chrome extension, if you load any page at different times you will get quite a few different results.

Please file issues with the extension against that repo: https://github.com/GoogleChrome/web-vitals-extension/

from web-vitals.

👍

from web-vitals.