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-dom-driver

v2.1.0

Published

A pullstream "webdriver" for interacting with changes to the dom.

Downloads

10

Readme

Build Status

pull-dom-driver

A pullstream "webdriver" for interacting with changes to the dom.

When you're testing client side apps like react or inu, finding and interacting with elements that appear dynamically is painful. pull-dom-driver uses a pull-stream source of dom mutations from pull-dom-mutants to find(".list") and click("#go-button") on elements once they're actually in the dom.

Usage

Let's find an element that isn't in the dom yet but will be:

//in the browser
var createDomStream = require('pull-dom-driver')
var pull = require('pull-stream')

var domStream = createDomStream(document, window)
pull(
  domStream.find('#mutant')
  pull.drain((elem) => console.log(`I found this: ${elem}`))
)

var myDiv = document.createElement('div')
myDiv.id = "mutant" 
document.body.appendChild(myDiv)

This will output

"I found this: [object HTMLDivElement]"

API

var createDomStream = require('pull-dom-driver')

createDomStream(rootElement)

Takes the rootElement on which you'd like to obseve changes.

var domStream = createDomStream(el)

Returns an object with the following keys:

  • subscribe
  • find
  • click

domStream.find(cssSelectorString)

Takes a cssSelectorString for the element(s) you'd like to find. Returns a pull-stream source of elements that have been found in the dom. Note that if there is an element that matches the selector when the stream is created it will be emitted by the stream first.

domStream.click(cssSelectorString)

Takes a cssSelectorString for the element(s) you'd like to click on. Returns a pull-stream source of elements that have been clicked in the dom. Note that if there is an element(s) that matches the selector when the stream is created it will be emitted by the stream first.

domStream.subscribe()

Returns a pull-stream source of dom mutations from pull-dom-mutants

Install

With npm installed, run

$ npm install pull-dom-driver

Acknowledgments

pull-dom-driver was inspired by..

See Also

License

MIT