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

@bazel/protractor

v5.8.1

Published

Run Protractor tests under Bazel

Downloads

24,211

Readme

Protractor rules for Bazel

The Protractor rules run tests under the Protractor framework with Bazel.

Installation

Add the @bazel/protractor npm package to your devDependencies in package.json.

Known issues with running Chromium for macOS/Windows in Bazel

For macOS and Windows, Chromium comes with files that contain spaces in their file names. This breaks runfile tree creation within Bazel due to a bug. There are various workarounds that allow for Chromium on these platforms:

  • Instruct Bazel to automatically disable runfile tree creation if not needed. More details here
  • Instruct Bazel to use an alternative experimental approach for creating runfile trees. More details here

protractor_web_test

USAGE

Runs a protractor test in a browser.

PARAMETERS

The name of the test

Protractor configuration file.

Defaults to None

A file with a node.js script to run once before all tests run. If the script exports a function which returns a promise, protractor will wait for the promise to resolve before beginning tests.

Defaults to None

JavaScript source files

Defaults to []

Other targets which produce JavaScript such as ts_library

Defaults to []

Runtime dependencies

Defaults to []

Optional server executable target

Defaults to None

Standard Bazel tags, this macro adds one for ibazel

Defaults to []

List of peer npm deps required by protractor_web_test

Defaults to ["@npm//@bazel/protractor", "@npm//protractor"]

A label providing the protractor entry point Default to :node_modules/protractor/bin/protractor.

Defaults to Label("@npm//:node_modules/protractor/bin/protractor")

passed through to protractor_web_test

protractor_web_test_suite

USAGE

Defines a test_suite of web_test targets that wrap a protractor_web_test target.

PARAMETERS

The base name of the test

A sequence of labels specifying the browsers to use.

Defaults to None

Data dependencies for the wrapper web_test targets.

Defaults to []

A list of test tag strings to use for the wrapped karma_web_test target.

Defaults to ["manual", "noci"]

Arguments for the wrapped karma_web_test target.