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

ng-vs-for

v1.2.6

Published

---

Downloads

3

Readme

ng-vs-for npm version


This is a port of https://github.com/kamilkp/angular-vs-repeat for Angular 4+


The name stands for Virtual Scroll For. It manipulates the collection you want to ngFor over in a way that only elements that are actually visible for the user are rendered in the DOM. So if you repeat over a thousand items only a few of them are rendered in the DOM, because the user can't see the rest anyway. And it takes time for the browser to render so many elements, which also might have some event listeners/bindings etc. So you should see a considerable boost in performance.

Installation

npm install ng-vs-for

Examples

Basic usage: all items shall have the same height

<div *vsFor="items; let _items = vsCollection">
    <div *ngFor="let item of _items">
        <!-- item html here -->
    </div>
</div>

Items have various sizes but they are known up front (calculatable based on their properties)

import { Component } from '@angular/core';

@Component({
  selector: 'some-component',
  template: `
        <div *vsFor="items; size:getSize; let _items = vsCollection">
            <div *ngFor="let item of _items">
                <!-- item html here -->
            </div>
        </div>

    `,
  inputs: ['items']
})
export class SomeComponent {
  items: any;
  getSize(item, index) {
    let size;
    // ... do some calculations here
    return size;
  }
}

The getSize could either be a number (or string castable to number) or a function on your component. If it's a function it will be called for each item in the original collection with two arguments: item (the item in the collection), and index (the index in the original collection). This function shall return a number - the height in pixels of the item.

Local variables

The vsFor directive is a structural directive and it exposes two local variables:

  • vsCollection - the sliced collection that should be assigned to a local variable and be used in ngFor
  • vsStartIndex - the index of the first element that is actually rendered (see last example at the bottom of the readme)

Parameters

Other parameters that you can pass to the vsFor directive:

  • offsetBefore (defaults to 0)
  • offsetAfter (defaults to 0)
  • excess (defaults to 2)
  • autoresize (set to true recalculates on window resize)
  • horizontal (hooks to scrolling horizontally and the optional size parameter calculates widths instead of heights)
  • tagName (defaults to div) - should be the same type as the tag name of the element you put the ngFor directive on
  • scrollParent (defaults to direct parent element) - a selector of the closest element that is the scrollable container for the repeated items. You can set window as a scroll parent in case the main window scrollbar should be used.

Example with some more parameters:

<table>
    <tbody *vsFor="items; size:getSize; tagName:'tr'; autoresize:true; scrollParent:'window'; excess:3; #_items = vsCollection; #_startIndex = vsStartIndex">
        <tr *ngFor="#item of _items; #i = index">
            {{ i + _startIndex }} <!-- the actual index in the original collection  -->
        </tr>
    </tbody>
</table>