npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

view-transitions-polyfill

v1.0.6

Published

A polyfill for the View Transitions API.

Readme

View Transitions API polyfill

A polyfill for the View Transitions API.

The polyfill is available on NPM.

Star this repo ⭐ on GitHub if you found it helpful!

Demo

View some demos showing example transitions.

A screen recording of some demos from the above link

Installation

Using npm

Install the polyfill in your project from npm:

npm install view-transitions-polyfill

Plain JS file

You may also download the polyfill's pre-built JS file from:

jsDelivr CDN

Get the polyfill from from jsDelivr:

Usage

Import the module into your site.

Inside a script (make sure it has type="module" in the <script> tag):

import 'view-transitions-polyfill';

Or from the HTML:

<script src="view-transitions-polyfill" async></script>

<!-- If the above does not work, try: -->
<script type="module">
  import 'view-transitions-polyfill';
</script>

[!NOTE]
Change the URLs in the above code snippets according to your use case.

  • Import from npm: view-transitions-polyfill
  • Import from plain JS file: ./view-transitions-polyfill.js (point it to the correct path for you)
  • Import from jsDelivr (version 1.0.5): https://cdn.jsdelivr.net/npm/[email protected]

Conditional loading

The above code snippets will always download the polyfill, whether the browser needs it or not. In order to only download the polyfill when needed, use the following code snippets.

Inside a script (make sure it has type="module" in the <script> tag):

if (!document.startViewTransition) {
  import('view-transitions-polyfill');
}

Or from the HTML:

<script type="module">
  if (!document.startViewTransition) {
    import('view-transitions-polyfill');
  }
</script>

[!NOTE]
Change the URLs in the above code snippets according to your use case.

  • Import from npm: view-transitions-polyfill
  • Import from plain JS file: ./view-transitions-polyfill.js (point it to the correct path for you)
  • Import from jsDelivr (version 1.0.5): https://cdn.jsdelivr.net/npm/[email protected]

With Astro View Transitions

You can use the polyfill with Astro view transitions by importing the script in the document as you would normally. For example, within a component:

<script src="view-transitions-polyfill"></script>

Compatibility

According to data from Can I use, the polyfill should be fully supported on:

  • Chrome ≥ 88
  • Edge ≥ 88
  • Opera ≥ 74
  • Safari ≥ 14
  • Firefox ≥ 78

This is because the polyfill currently requires the browser to support these notable features:

Development

Building

Build the polyfill to dist:

npm run build

Testing

To test the polyfill, you can run Web Platform Tests. You need to set up your system before running tests.

Run the tests with:

npm run test

This will generate report files in test/report.

The polyfill only loads its functions into the browser if it does not already natively support the View Transitions API. You can run the tests with a version of the polyfill that avoids this check with:

npm run test-always-polyfill

You can view the tests' web pages in your browser with:

npm run test-debug

Optimizing test performance

It is recommended that you run the tests like this:

npm run test -- --processes <number of threads> -f --exclude css/css-view-transitions/navigation
  • --processes and -f introduce parallelism to make the tests run faster.
  • --exclude makes it so that Navigation API tests are ignored, since they will always fail on some browsers (e.g. Firefox) which do not implement that API.

[!NOTE] More command line options are documented on the web platform tests documentation.

You can also add these arguments to npm run test-always-polyfill.

Performance measurement

A version of the polyfill set up to measure its performance can be found at the performance branch. You can follow the associated instructions.