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 🙏

© 2024 – Pkg Stats / Ryan Hefner

content-visibility

v1.2.2

Published

A web component leverages CSS content-visibility and the Intersection Observer API to provide cross browsers content-visibility solution

Downloads

2,276

Readme

content-visibility

Published on webcomponents.org npm 7.0.15 Typescript Lit-Element

<content-visibility> is a simple web component encapsulates modern CSS properties content-visibility and Web API Intersection Observer API to provide cross-browsers solution to skip rendering (layout & painting) elements until it is needed (appears on the viewport) to boosts page performance.

CSS content-visibility is only supported on Chrome 85+, Chrome Android 85+ and Opera 71+ but not Firefox, Safari and IE unfortunately, see web.dev. Intersection Observer API supports pretty much all browsers except IE, thus an intersection observer polyfill is included for compatible on IE.

Basically, all children inside it will only be renderred after it appears on viewport.

<content-visibility>
  {children will not be rendered when outside the first viewport}
</content-visibility>

Compatibility

Getting started

Install

npm i content-visibility --save

Use in JSX (React/Preact)

import 'content-visibility';

const Content = () => {
  return (
    <content-visibility>
      <Section>...</Section>
      <Section>...</Section>
      <Section>...</Section>
    </content-visibility>
  );
};

properties

containIntrinsicSize

This is will be set as CSS custom variable for contain-intrinsic-size if browsers support it. see

<content-visibility containIntrinsicSize="600px">
  {children}
</content-visibility>

Performance results

Rendering frames

Safari comes with Rendering Frames Timeline tool helps to measure rendering performance. Let's have a look the rendering frames without <content-visibility>, total 97 rendering frames happened on the first view. Rendering Frames - no content-visibility

Only 47 rendering frames happened on the first view after integrated with <content-visibility> Rendering Frames - content-visibility the rest of 50 rendering frames happened when scorlling to the viewport Rendering Frames - content-visibility scroll

Rendering & Layout time

Generally speaking, we can plausibly say rendering & layout time improved around 40%, however benchmark results vary depends on sampling size, environments, tools, implementation and etc. Too many factors could impact benchmark results, so this is just a quick sample results to demonstrate the performance differences.

Chrome 87.0.4280.141

CSS content-visibility and contain-intrinsic-size

Before

Chrome Before

After

Rendering and Painting time reduced around 50%.

Chrome After

Firefox 84.0.2

Before

Firefox Before

After

Firefox After

License

Copyright (c) 2021 Brian YP Liu