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

@orangebeard-io/javascript-client

v2.0.5

Published

Orangebeard client for JavaScript

Downloads

525

Readme

Installation

Install the npm package

npm install --save-dev @orangebeard-io/javascript-client

Build from source

npm run build

Make sure to have typescript installed.

Configuration

Usually, the client is used from a listener that connects the client to a test tool. Listeners can provide their own OrangebeardParameters object.
If no configuration object is provided, the client will try to auto-configure in the following ways:

orangebeard.json

Look for a config file named orangebeard.json in the current working directory or higher in the hierarchy (it will scan all the way up to /). The json file is expected to contain an OrangebeardParameters object:

{
   "endpoint": "https://my.orangebeard.app",
   "token": "xxxxxxxxxxxxx-xxxx-xxxx-xxxxxxxxxxxx",
   "project": "my-project",
   "testset": "Test set name",
   "description": "Test run description",
   "attributes": [
   	{
   		"key": "Key 1",
   		"value": "Some value"
   	},
   	{
   		"value": "Tag value"
   	}
   ]
}

Environment variables

The auto config will scan for environment variables:

ORANGEBEARD_ENDPOINT=https://company.orangebeard.app
ORANGEBEARD_TOKEN=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
ORANGEBEARD_PROJECT=piet_personal
ORANGEBEARD_TESTSET=piet_TEST_EXAMPLE
ORANGEBEARD_DESCRIPTION=My awesome testrun
ORANGEBEARD_ATTRIBUTES=key:value; value;

Note that if auto configuration is used and a value is present in both orangebeard.json and in the environment settings, the environment setting will take precedence.