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

q-proxy

v0.0.1

Published

A promise wrapper that proxies future method calls.

Downloads

14

Readme

QProxy

QProxy wraps JavaScript promises (Promises/A spec, e.x. Q) to allow you to chain arbitrary method calls before proxy is resolved.

For example, normally with the wd WebDriver library you would need to do the following:

browser.elementById("email").then(function(element) {
  element.type("[email protected]");
});

With QProxy you can do the following:

QProxy(browser).elementById("email").type("[email protected]")

Once the result of elementById is resolved the type method will actually be called with the correct arguments. The whole expression returns a promise which is resolved after both the elementById and subsequent type invocations are resolved.

With a sequential helper library such as QStep you could do the following (CoffeeScript):

browser = QProxy(wd.promiseRemote("localhost", 4444))
QStep(
  -> browser.init(browserName: "firefox")
  -> browser.get("https://www.facebook.com/")
  -> browser.elementById("email").type(credentials.email)
  -> browser.elementById("pass").type(credentials.password)
  -> browser.elementById("u_0_b").click()
)