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

universal-gallery

v1.0.1

Published

Super generic base gallery that can be styled to pretty much any layout & animation you'll ever need.

Downloads

3

Readme

universal-gallery

A package within web-sparkle.

Super generic, unopinionated base gallery that can be styled to pretty much any layout & animation you'll ever need.

Usage

$ npm install universal-gallery
<div id="gallery">
  <div class="slide">Slide 1</div>
  <div class="slide">Slide 2</div>
  <div class="slide">Slide 3</div>
  <div class="slide">Slide 4</div>
  <div class="slide">Slide 5</div>
</div>
const UniversalGallery = require('universal-gallery')

const $gallery = document.getElementById('gallery')

const handleSlide = (index, indexWithClones) => {
  // Do stuff with this information!
  // Ex. trigger another gallery to change slides
}

const gallery = new UniversalGallery({
  galleryNode: $gallery,    // DOMElement that is the parent container for your slides
  childSelector: '.slide',  // A CSS selector to grab your slides
  numOfClones: 1,           // Useful if you only have a few slides (explained further below)
  shouldAutoplay: true,     // Toggle autoplay (obvi)
  slideSpeed: 3000,         // Duration between each slide change (in milliseconds)
  handleChange: handleSlide // Called every time the slide index changes
})

Reference

The idea behind this gallery is that it's the most unopinionated, generic base. All we have is the bare-bones, core functionality:

  • Change slide index (next, previous, or go to a specific one)
  • Play / Pause
  • Mark DOM Elements with "arrival" and "departure" indices (the previous slide has a departure index of 1, the current slide has arrival and departure indice of 0, and the next slide has an arrival index of 1, etc.)

All the styling can be done in the CSS, using [data-arrival-index="n"] and [data-departure-index="n"] as selectors. This is (usually) going to be more performant than animating via JS, and also allows you to use this same exact base gallery for all kinds of visually different gallery elements.

new UniversalGallery(config)

Create a new instance of UniversalGallery. Pass in a config object, as specified below.

Param: config object

- galleryNode {DOMElement}     | The container element. [REQUIRED]
- childSelector {String}       | The selector for each element that should be updated. [REQUIRED]
- numOfClones {Number}         | How many clones we should make.
- slideSpeed {number}          | Number of milliseconds between slide changes
- shouldAutoplay {Boolean}     | Should it autoplay?
- handleChange {Function}      | Callback method on update, supplied with the current index (disregarding
                                 clones), and the index including clones.

Development

To run the example locally, run the following commands:

npm install
npm run dev
npm start

Credits

This readme is maintained by [email protected].


License

MIT