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

pull-scroll

v1.0.9

Published

pull-stream to a infinite scrolling web pane.

Downloads

32

Readme

pull-scroll

pull-stream to a infinite scrolling web pane.

streams are for programatically dealing with data that arrives or is processed over time. Many applications also have features they call "streams", or views that may contain a large number of items, if you just keep scrolling down?

pull-scroll is the simplest way to join these concepts, you can take a pull-stream of content, attach it to a scrolling element, and the scroller sets the back pressure.

when the element is filled, back pressure kicks in, and when you scroll to the end, it is released, and more data flows in.

pull-scroll can be used for both double and single ended content streams.

example

var Scroller = require('pull-scroll')
var pull = require('pull-stream')
var h = require('hyperscript')

var content = h('div')
var scroller = h('div', {
    style: {
      //must set overflow-y to scroll for this to work.
      'overflow-y': 'scroll',
      //and cause this element to not stretch.
      //this can also be achived using flexbox column.
      position: 'fixed', bottom:'0px', top: '0px',
      width: '600px'
    }
  }, content)

  //provide a render function that returns an html element.
  function render (n) {
    return h('h1', n.toString())
  }

  pull(
    pull.infinite(),
    Scroller(scroller, content, render)
  )

document.body.appendChild(scroller)

you can have attach two Scrollers to an element, one for scrolling up and one for scrolling down. (thus, a two way infinite scroller)

see example here

api

Scroller(scrollable, container, render, isPrepend, isSticky, cb) => Sink

Create a pull-stream sink where the back pressure is controlled by the scrolling of the element. scrollable needs to be an element which can scroll, and container is an optional child (otherwise elements will be added directly to scrollable)

render is a function that takes stream items and returns an html element.

If isPrepend is true, elements will be added before the first child of container, if it is false, they will be appended.

If isSticky is true, scrollable will be scrolled into position after adding an element. this will make more elements come automatically, untill you scroll away. If isSticky is false, new elements will extend the container, but not be scrolled into positon, this means the scroll will only be adjusted as the user scrolls.

If the user is scrolling to read old data (i.e. scrolling down on twitter, or up in the terminal) then use isSticky=false. If the user is scrolled to the end to get new data, (i.e. scrolling to the top on twitter, or the bottom in the terminal) then use isSticky=true.

cb is an optional callback used only for error handling. This defaults to

function (err) { if(err) console.error(err) }

License

MIT