https://github.com/bahrus/be-lazy
be-lazy loads a template into the live DOM tree only when it becomes visible (or is about to be visible based on threshold settings.)
https://github.com/bahrus/be-lazy
Last synced: 2 months ago
JSON representation
be-lazy loads a template into the live DOM tree only when it becomes visible (or is about to be visible based on threshold settings.)
- Host: GitHub
- URL: https://github.com/bahrus/be-lazy
- Owner: bahrus
- License: mit
- Created: 2022-03-02T22:07:17.000Z (over 3 years ago)
- Default Branch: baseline
- Last Pushed: 2024-08-02T11:48:10.000Z (10 months ago)
- Last Synced: 2025-03-19T12:07:24.698Z (3 months ago)
- Language: JavaScript
- Homepage:
- Size: 332 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# be-lazy (🦥)
[](https://github.com/bahrus/be-lazy/actions/workflows/CI.yml)
be-lazy loads a template into the live DOM tree only when it becomes visible (or is about to be visible based on threshold settings.)
Size of package, including custom element behavior framework (be-decorated):
[](https://bundlephobia.com/result?p=be-lazy)
Size of new code in this package:
The consumer of be-lazy needs to use css to set the size to something approximating what it will be when instantiated:
```html
template[be-lazy], template[is-lazy]{
display:block;
height: 18px;
}
I am here
```
The role of be-lazy ends once it becomes viewable, and the content is instantiated. In fact, the template is deleted at that point.
Options include setting [IntersectionObserverInit](https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API#creating_an_intersection_observer) settings:
```html
```
Other configuration settings include "enterDelay" and "exitDelay". The idea behind those settings is if the user is scrolling very quickly, it can slow the scrolling down if it is instantiating templates that have already zoomed past.
be-lazy can hold its own against [content-visibility](https://web.dev/content-visibility/) in terms of performance.
It is most effective if content is "paged" -- be-lazy really shouldn't hold a single div tag as shown above, but the amount of content inside should approximately fill the screen.
be-lazy is currently being used by one virtual list - [xtal-vlist](https://github.com/bahrus/xtal-vlist).
## Viewing this element locally
Any web server than can serve static files will do, but...
1. Install git.
2. Fork/clone this repo.
3. Install node.
4. Open command window to folder where you cloned this repo.
5. > npm install
6. > npm run serve
7. Open http://localhost:3030/demo/dev in a modern browser.
## Running Tests
```
> npm run test
```
## Using from CDN:
```html
import 'https://esm.run/be-lazy';
```
## Referencing via ESM Modules:
```JavaScript
import 'be-lazy/be-lazy.js';
```