
Security News
The Changelog Podcast: Practical Steps to Stay Safe on npm
Learn the essential steps every developer should take to stay secure on npm and reduce exposure to supply chain attacks.
@fastly/performance-observer-polyfill
Advanced tools
🔎 PerformanceObserver Polyfill <img alt="Travis" src="https://img.shields.io/travis/fastly/performance-obs
The PerformanceObserver interface is a JavaScript API that can be used to observe the Performance Timeline to be notified of new performance metrics as they are recorded.
This polyfill allows consumers to use the PerformanceObserver interface within browser environments, which have basic Performance Timeline support (I.e. window.performance.getEntries()), but don't have observer support.
The polyfill works by falling back to polling the Performance Timeline on a given interval and calling all subscribed observers with the resulting set of entires.
npm install --save @fastly/performance-observer-polyfill
This automatically "installs" PerformanceObserverPolyfill as window.PerformanceObserver() if it detects PerformanceObserver isn't supported:
import '@fastly/performance-observer-polyfill/polyfill'
// PerformanceObserver is now available globally!
const observer = new PerformanceObserver((list) => {});
observer.observe({entryTypes: ['resource']});
With a module bundler like rollup or webpack,
you can import @fastly/performance-observer-polyfill to use in your code without modifying any globals:
// using JS Modules:
import PerformanceObserver from '@fastly/performance-observer-polyfill'
// or using CommonJS:
const PerformanceObserver = require('@fastly/performance-observer-polyfill')
// usage:
const observer = new PerformanceObserver((list) => {});
observer.observe({entryTypes: ['resource']})
As the polyfill implements the PerformanceObserver interface by falling back to polling the Performance Timeline via a call to window.performance.getEntries() we are limited to only expose timeline entry types that are supported by getEntries(). Therefore the polyfill can only be used to observe the entry types: navigation, resource and mark. Newer entry types such as paint are only exposed by the native PerformanceObserver implementation and thus not polyfillable.
git clone git@github.com:fastly/performance-observer-polyfill.git
cd performance-observer-polyfill
npm install
npm run build
Most actions you'd like to perform whilst developing performance-observer-polyfill are defined as NPM scripts tasks and can be invoked using npm run {task}.
A list of all commands and their description can be found below.
| Name | Description |
|---|---|
| build | Compiles the application for production environments |
| build:dev | Compiles the application for development |
| lint | Lints the source files for style errors using ESLint and automatically formats the source files using prettier |
| test | Runs the unit test suite |
FAQs
🔎 PerformanceObserver Polyfill <img alt="Travis" src="https://img.shields.io/travis/fastly/performance-obs
We found that @fastly/performance-observer-polyfill demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 51 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Learn the essential steps every developer should take to stay secure on npm and reduce exposure to supply chain attacks.

Security News
Experts push back on new claims about AI-driven ransomware, warning that hype and sponsored research are distorting how the threat is understood.

Security News
Ruby's creator Matz assumes control of RubyGems and Bundler repositories while former maintainers agree to step back and transfer all rights to end the dispute.