browserstack-runner 0.0.1

A command line interface to run browser tests over BrowserStack

browserstack-runner@0.0.1 was published on 2013-08-02. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

Deprecated: browserstack-runner is deprecated and no longer maintained. Migrate to the BrowserStack SDK. See https://www.browserstack.com/docs/automate/selenium/sdk-benefits

All browserstack-runner versions · Permanent reference to 0.0.1 · Latest release

Package specifications

Version0.0.1
License declarationNot declared
Published2013-08-02T07:35:29.846Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories2
Resolved graph dependencies0
Repository starsUnknown
Repository forksUnknown

Install browserstack-runner 0.0.1

npm install browserstack-runner@0.0.1
pnpm add browserstack-runner@0.0.1
yarn add browserstack-runner@0.0.1

Runtime dependencies

  • browserstack git://github.com/browserstack/node-browserstack.git

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

    How to interpret the specifications

    Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

    Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

    Known direct advisories

    Evidence and freshness