[![npm](http://img.shields.io/npm/v/zeugberg.svg?style=flat-square)](https://npmjs.com/zeugberg) [![npm downloads](http://img.shields.io/npm/dm/zeugberg.svg?style=flat-square)](https://npmjs.com/zeugberg) [![build status](http://img.shields.io/travis/jher

Usage no npm install needed!

<script type="module">
  import zeugberg from 'https://cdn.skypack.dev/zeugberg';


Zeugberg /tsɔʏ̯kbɛʁk/

npm npm downloads build status

Install via npm

$ npm install -g zeugberg


$ zeugberg [options]

To run zeugberg in full debug mode:

$ env DEBUG="*" zeugberg
  --help, -h      Show help
  --version, -v   Show version number
  --pattern, -p   Test glob pattern                                        [default: "test/**/*.js"]
  --reporter, -r  Test reporters to use (can be specified multiple times)  [default: "tap"]
  --proxy         Set the proxy configuration
  --debug         Enable debugging output                                  [default: false]

Chromium CLI Options

Additionally, all switches supported by Content API of Chromium, as well as some nw.js specific switches:

  • --data-path: Override the default data path (where cookies and localStorage etc. reside)
  • --disable-gpu --force-cpu-draw: force the drawing / compositing using cpu (needed for click through transparency), see nw.js/wiki/Transparency.

For details see nw.js/wiki/Command-line-switches.

Proxy Configuration

Parses the rules from a string, indicating which proxies to use.

proxy-uri = [<proxy-scheme>"://"]<proxy-host>[":"<proxy-port>]
proxy-uri-list = <proxy-uri>[","<proxy-uri-list>]
url-scheme = "http" | "https" | "ftp" | "socks"
scheme-proxies = [<url-scheme>"="]<proxy-uri-list>
proxy-rules = scheme-proxies[";"<scheme-proxies>]

Thus, the proxy-rules string should be a semicolon-separated list of ordered proxies that apply to a particular URL scheme. Unless specified, the proxy scheme for proxy-uris is assumed to be http.

Some special cases:

  • If the scheme is omitted from the first proxy list, that list applies to all URL schemes and subsequent lists are ignored.
  • If a scheme is omitted from any proxy list after a list where a scheme has been provided, the list without a scheme is ignored.
  • If the url-scheme is set to socks, that sets a fallback list that to all otherwise unspecified url-schemes, however the default proxy-scheme for proxy urls in the 'socks' list is understood to be socks4:// if unspecified.

For example:

"http=foopy:80;ftp=foopy2"  -- use HTTP proxy "foopy:80" for http://
                               URLs, and HTTP proxy "foopy2:80" for
                               ftp:// URLs.
"foopy:80"                  -- use HTTP proxy "foopy:80" for all URLs.
"foopy:80,bar,direct://"    -- use HTTP proxy "foopy:80" for all URLs,
                               failing over to "bar" if "foopy:80" is
                               unavailable, and after that using no
"socks4://foopy"            -- use SOCKS v4 proxy "foopy:1080" for all
"http=foop,socks5://bar.com -- use HTTP proxy "foopy" for http URLs,
                               and fail over to the SOCKS5 proxy
                               "bar.com" if "foop" is unavailable.
"http=foopy,direct://       -- use HTTP proxy "foopy" for http URLs,
                               and use no proxy if "foopy" is
"http=foopy;socks=foopy2   --  use HTTP proxy "foopy" for http URLs,
                               and use socks4://foopy2 for all other

See nw.js/wiki/App#setproxyconfigconfig

Running Zeugberg on Travis CI

See Travis CI Docs