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

webcomponents-lazy-img

v1.0.0

Published

Lazy loading img element

Downloads

2

Readme

Published on webcomponents.org

Demo and API docs

<lazy-image>

lazy-img is a lazy loading img element that is shadow-dom friendly and uses IntersectionObserver to detect when images are within the viewport and need to be loaded.

The default behavior is to use the browser viewport but more specific control can be provided by setting the observe property to a parent selector (either an element id, class or tag name):

<div id="myscroller">
        <lazy-img src="image1.jpg" observe="#myscroller"></lazy-img>
        <lazy-img src="image2.jpg" observe="#myscroller"></lazy-img>
        ...
        <lazy-img src="image99.jpg" observe="#myscroller"></lazy-img>
<div>

margin and threshold allow control over exactly when the loading is triggered as the element comes into view. margin can reduce or extend the detection area of the container and threshold can determine what proportion of the image needs to be within the area.

Demo is based on this example of intersection-observer

If used on a browser without support for IntersectionObserver a polyfill will be loaded automatically from the polyfill.io service.

Configure this with the following code in index.html:

<script>
  // Define polyfills for features that our app depends on:
  window.PolyPoly = {
    features: []
  };
  ('IntersectionObserver' in window) || window.PolyPoly.features.push('IntersectionObserver');
</script>