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

@best/agent

v12.0.2

Published

Best Agent

Downloads

45

Readme

Best Hub

A Best agent is a machine used to run BEST tests in an isolated environment, ensuring nothing changes. The agent usually runs with an specific best runner (ex: @best/runner-headless or @best/runner-webdriver) with the specific config

Starting the agent

Registration with a hub

When the best agent starts, if env.HUB_CONFIG is set, it will try to auto register with the specified hub.

env.HUB_CONFIG is a JSON string representing an object in the following form:

const hubConfig = {
    hub: {
        // Hub Connection settings.
        host: 'http://localhost:6000',
        authToken: 'agent token used for authentication with the hub',
        pingTimeout: 180000, // Optional: 180000ms (3 minutes) is the default ping timout.
    },
    agentConfig: {
        spec: {
            // Only benchmarks with this spec can run in this agent.
            browser: 'chrome',
            version: '76',
        },
        host: 'http://localhost:5000', // Required. Url used by the hub to connect to this agent.
        options: { path: '/best' }, // Connection Options
        remoteRunner: '@best/runner-headless', // Required. The runner which this agent will use when running the job.
        remoteRunnerConfig: {}, // Required (may be an empty object). The Runner config for this agent.
    },
};

// set env.HUB_CONFIG=JSON.stringify(hubConfig)

Communication registration process between the agent and the hub

When the agent starts, with a hub config, it will start the communication with the hub in the following protocol:

  1. Every hubConfig.pingTimeout the agent will do a ping request to the hub, and the hub can reply with
    1. registered=false. In this case the hub will make a request to register with the hub (2)
    2. registered=true. Nothing to do, the hub already has this agent registered.
    3. authentication failed. Any further communication is suspended since the connection token is invalid.
  2. Register agent with hub: the hub will return a status.code 201 in case of success, a different status code on failure to register the agent.