From 82f2b76e25a4a67e01ec67e5ebe39d14ad771ea8 Mon Sep 17 00:00:00 2001 From: Florian Dold Date: Thu, 20 Apr 2017 03:09:25 +0200 Subject: Reorganize module loading. We now use webpack instead of SystemJS, effectively bundling modules into one file (plus commons chunks) for every entry point. This results in a much smaller extension size (almost half). Furthermore we use yarn/npm even for extension run-time dependencies. This relieves us from manually vendoring and building dependencies. It's also easier to understand for new developers familiar with node. --- node_modules/selenium-webdriver/chrome.js | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'node_modules/selenium-webdriver/chrome.js') diff --git a/node_modules/selenium-webdriver/chrome.js b/node_modules/selenium-webdriver/chrome.js index eb33df9ed..2dbc93351 100644 --- a/node_modules/selenium-webdriver/chrome.js +++ b/node_modules/selenium-webdriver/chrome.js @@ -59,7 +59,7 @@ * let options = new chrome.Options(); * // configure browser options ... * - * let driver = new chrome.Driver(options, service); + * let driver = chrome.Driver.createSession(options, service); * * Users should only instantiate the {@link Driver} class directly when they * need a custom driver service configuration (as shown above). For normal @@ -595,7 +595,7 @@ class Options { * let options = new chrome.Options().setMobileEmulation( * {deviceName: 'Google Nexus 5'}); * - * let driver = new chrome.Driver(options); + * let driver = chrome.Driver.createSession(options); * * __Example 2: Using Custom Screen Configuration__ * @@ -605,7 +605,7 @@ class Options { * pixelRatio: 3.0 * }); * - * let driver = new chrome.Driver(options); + * let driver = chrome.Driver.createSession(options); * * * [em]: https://sites.google.com/a/chromium.org/chromedriver/mobile-emulation -- cgit v1.2.3