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

testlabs-grid

v0.1.0

Published

This is a basic re-implementation of the Selenium Grid in node.js.

Downloads

14

Readme

TestLabs Grid

This is a basic re-implementation of the Selenium Grid in node.js.

Please take a look at the code, feel free to fork it, modify it and use it for whatever you like - and we always appreciate issue reports and pull requests!

Why?

We did this primarily to allow us to scale the grid easily and efficiently - the core implementation for example reads all responses in to memory before relaying them back to your code.

Usage

You can start the grid by running node grid.js. By default it will start listening on port 3000.

Access to an admin section is available at http://localhost:3000/admin with the username and password admin/password.

When writing Selenium tests you use RemoteWebDriver in the same way as you would with the Java Selenium grid.

You can reconfigure some basics by modifying config/{environment}.js and then running the grid with NODE_ENV={environment} node grid.js