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

protractor-webpack

v1.1.0

Published

Synchronizes Protractor test runs with serving a Webpack bundle

Downloads

66

Readme

protractor-webpack

Installation

npm install --save-dev protractor-webpack

Programatic Usage

The run function will serve the Webpack bundle and run the Protractor tests. It requires two arguments: the Webpack config as a JSON object and the path to the Protractor config.

var webpackConfig = require('./webpack.config.json');
var runner = require('protractor-webpack');

runner.run('./protractor.conf.js', webpackConfig);

CLI Usage

TODO - Add documentation

Credit

This project is heavily influenced by the work done in angular-cli. They use the webpack-dev-server to serve the application for test and call to the Protractor launcher directly to execute the tests. To wire everything together, they simply create a callback function to launch the protractor test and synchronize it with the webpack build by passing it is a plugin on 'done'.

The issue with angular-cli is that it blindly refuses to build an ejected project, and rather than allow for running the tests from the webpack config.