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

browser-task

v0.55.0

Published

Do stuff in other peoples' browsers

Downloads

30

Readme

Do stuff in other peoples' browsers with browser-task.

Start a server:

cd ~
npm install browser-task
node browser-task/start

That should open http://localhost:9777/browser in your web browser, so that there is a worker in the queue available to do tasks.

Add a task with the API:

var browserTask = require("browser-task")

var browser = browserTask(
  "http://localhost:9777",
  function() {
    browser.pressButton(".go", thenExpectSomething)})

function thenExpectSomething() {
  browser.assertText(".my-div", "BANG!",
  thenBeDone)}
  
function thenBeDone (){
  browser.done()}

Methods

browser.assertHasClas("#my-selector", "some-class-name", callback)
browser.assertNoClass(...)
browser.pressButton("#some-button", callback)
browser.done()

Screencast

Screencast of running npm start in the browser-task folder in the console, then when the worker opens in the browser, running the browser-bridge tests to demonstrate browser-task doing stuff

Notes

review every command, at least the first few for each user

flag things with adjectives

User 2354: [auto-declined message with prurient content]

Why

  • you always get to a point when you want to pause the test and look in the browser anyway

  • it works on any browser you want, so you can use it for testing too

  • I will need it for screencasting tests, customer support, etc anyway

  • iframe stuff doesn't work in zombiejs. In general there are holes in the zombie/jsdom coverage

  • jsdom uses ES6. Also it is a nightmare.

  • zombie uses ws which uses bufferutils which compiles stuff and slows down npm installs dramatically