⛔ This project is deprecated, please consider using Puppeteer instead. ⛔

NickJS predates Puppeteer and is no longer the best tool around. This project isn't maintained anymore.

Web scraping library made by the Phantombuster team. Modern, simple & works on all websites.

NickJS.org — Inline doc ↓

• Supports both Headless Chrome and PhantomJS as drivers
• Simple high-level API
• Async/await, Promises and callback coding styles

NickJS allows you to automate navigation and collect data from any website. By controlling an instance of either Headless Chrome or PhantomJS with CasperJS, your bots will simulate a human.

It's simple and allows for an easy implementation of our 3 scraping steps theory.

const Nick = require("nickjs")
const nick = new Nick()

;(async () => {

	const tab = await nick.newTab()
	await tab.open("news.ycombinator.com")

	await tab.untilVisible("#hnmain") // Make sure we have loaded the page

	await tab.inject("http://code.jquery.com/jquery-3.2.1.min.js") // We're going to use jQuery to scrape
	const hackerNewsLinks = await tab.evaluate((arg, callback) => {
		// Here we're in the page context. It's like being in your browser's inspector tool
		const data = []
		$(".athing").each((index, element) => {
			data.push({
				title: $(element).find(".storylink").text(),
				url: $(element).find(".storylink").attr("href")
			})
		})
		callback(null, data)
	})

	console.log(JSON.stringify(hackerNewsLinks, null, 2))

})()
.then(() => {
	console.log("Job done!")
	nick.exit()
})
.catch((err) => {
	console.log(`Something went wrong: ${err}`)
	nick.exit(1)
})

First of all, install NickJS: npm install nickjs.

NickJS will choose which headless browser to use depending on how you launch it. When launching your script with node, Headless Chrome will be used. When launched with casperjs, CasperJS+PhantomJS will be used.

To get started with the PhantomJS driver, read this. However we recommend using Headless Chrome (read on).

You'll need to have Node 7+ and Chrome 63+ installed on your system (read the next section for more info about which Chrome version you should use). The path to the Chrome executable can be specified with export CHROME_PATH=/path/to/chrome otherwise the binary google-chrome-beta will be used.

Launching a bot is then as simple as node my_nickjs_script.js.

NickJS makes use of the latest DevTools protocol methods, so you'll need a very recent version of Chrome.

At the time of writing, NickJS is using some methods from Chrome 63, which is the Beta Channel. Having the correct version of Chrome is critical for a smooth experience with NickJS. Go to the Chrome Release Channels page and download a version compatible with your system. If you want this to be taken care of for you, check out Phantombuster, which is basically our "NickJS as a service" platform.

The following environment variables have an effect on NickJS:

• CHROME_PATH: specifies where to find the Google Chrome binary — this is important! Example: "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome"
• NICKJS_LOAD_IMAGES (0 or 1): disables image loading (equivalent to NickJS' constructor option loadImages)
• NICKJS_NO_SANDBOX (0 or 1): disables Chrome's sandboxing (no effect when the CasperJS+PhantomJS driver is used)
• NICKJS_PROXY or http_proxy: see below

NickJS supports HTTP (and HTTPS) proxies. Other protocols are not yet supported. To specify which proxy to use, set the httpProxy option in NickJS' constructor. You can also set the environment variable NICKJS_PROXY or the standard http_proxy (but the constructor option takes precedence).

Your proxy must be specified in the following format: http://username:[email protected]:3128 (the protocol portion is optional).

Contrary to some other libraries, yes, NickJS supports proxy authentication with Headless Chrome.

• Nick
  • Nick()
  • deleteAllCookies()
  • deleteCookie()
  • driver
  • exit()
  • getAllCookies()
  • newTab()
  • setCookie()
• Nick tab
  • click()
  • close()
  • evaluate()
  • fill()
  • getContent()
  • getUrl()
  • inject()
  • isPresent()
  • isVisible()
  • onConfirm
  • onPrompt
  • open()
  • screenshot()
  • scroll()
  • scrollToBottom()
  • sendKeys()
  • wait()
  • waitUntilPresent()
  • waitUntilVisible()
  • waitWhilePresent()
  • waitWhileVisible()

This is Nick's constructor. options is an optional argument that lets you configure your Nick instance.

Nick must be instantiated only once. Behind the scenes, the headless browser driver is initialized. The next step is to open a tab with newTab().

Optional settings for the Nick instance.

• printNavigation (Boolean): when true (the default), Nick will log important navigation information like page changes, redirections and form submissions
• printResourceErrors (Boolean): when true (the default), Nick will log all the errors encountered when loading pages, images and all other resources needed by the pages you visit
• printPageErrors (Boolean): when true (the default), Nick will log all JavaScript errors and exceptions coming from the scripts executed in the page context
• resourceTimeout (Number): milliseconds after which Nick will abort loading a resource (page, images and all other resources needed by the pages you visit)
• userAgent (String): sets the User-Agent header
• loadImages (Boolean): whether or not to load the images embedded in the pages (defaults to true) (note: specifying this parameter overrides the agent's Phantombuster setting "Load Images")
• blacklist (Array): soon!
• whitelist (Array): soon!
• childStdout (String): when stderr can redirect stdout to stderr
• childStdout (String): when stdout can redirect stderr to stdout
• additionalChildOptions (Array): When chrome is used this is an Array of string (e.g ["--ignore-certificate-errors", "--ignore-urlfetcher-cert-requests"]), for CasperJs though this is an array of objects (e.g [{verbose: true, logLevel: "debug" }])

const Nick = require("nickjs")
const nick = new Nick()

const Nick = require("nickjs")

// these are the default options
const nick = new Nick({
  printNavigation: true,
  printResourceErrors: true,
  printPageErrors: true,
  timeout: 10000,
  userAgent: "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36"
})

Deletes all cookies set to the headless browser.

Function called when finished(optional).

• err (String): null or a description of what went wrong if something went wrong

try {
  await nick.deleteAllCookies()
  // All cookies are cleanded up
} catch (err) {
  console.log("Could not delete all cookies:", err)
}

This method will delete all cookies that might be necessary to your bot.

Deletes a specific cookie set in the headless browser.

Function called when finished(optional).

• err (String): null or a description of what went wrong if something went wrong.

const cookieName = "cookieName"
const cookieDomain = ".domain.com"

try {
  await nick.deleteCookie(cookieName, cookieDomain)
} catch (err) {
  console.log("Could not delete cookie:", err)
}

nick.driver lets you access the underlying headless browser driver instance that is being used by Nick.

This is useful when doing trickier things in your navigation and for accessing driver-specific methods that are not available in Nick.

// In this case we're using the PhantomJS+CasperJS driver
// This gets the CasperJS instance and clears the cache
nick.driver.casper.page.clearMemoryCache()

Immediately stops the whole bot and exits the process with code.

Optional exit code that the process should return. 0 by default.

nick.exit() // All is well

nick.exit(1) // Something went horribly wrong

Gets an object containing all cookies set in the headless browser.

Function called when finished(optional).

• err (String): null or a description of what went wrong if something went wrong.
• cookies (PlainObject): an object containing all cookies of the headless browser and their properties

try {
  const cookies = await nick.getAllCookies()
  // Cookies contain all your cookies
  console.log(cookies, null, 2)
} catch (err) {
  console.log("Could not get all cookies:", err)
}

Opens a new tab.

This is the first step in manipulating a website.

To open multiple tabs, call this method multiple times. If your bot opens many tabs to do different tasks, it's a good idea to close() them when their work is finished (to keep memory usage down).

try {
  const tab = await nick.newTab()
  // You can now browse any website using `tab`
} catch (err) {
  console.log("An error occured:", err)
}

Sets a cookie.

Set the name, the value and the domain of a cookie. This cookie can be seen with getAllCookies() and deleted with deleteAllCookies() or deleteCookie().

An object containing all attributes of a cookie.

• name (String): Name of the cookie you want to set.
• value (String): Value of the cookie you want to set.
• domain (String): Domain linked to the cookie set.

Function called when finished(optional).

• err (String): null or a description of what went wrong if something went wrong.

const cookie = {
  name: "cookieName",
  value: "cookieValue",
  domain: ".domain.com"
}

try {
  await nick.setCookie(cookie)
  // You can navigate with your cookie set
} catch (err) {
  console.log("Could not create cookie:", err)
}

Performs a click on the element matching the CSS selector selector.

Clicking on elements is one of the main ways to manipulate web pages with Nick. Clicking is an easy way to navigate where you want, but keep in mind that it can be more efficient to scrape URLs (for example with evaluate()) and then call open().

CSS selector targeting what element to click. Probably a button or an a but can be anything you want. Make sure the target element is visible or present by calling waitUntilVisible() or waitUntilPresent() beforehand.

Function called when finished (optional).

• err (String): null or a string describing what went wrong with the click (typically the CSS selector did no match any element)

const selector = "button.cool-button"
const pageTimeout = 5000

try {
  await tab.waitUntilPresent(selector, pageTimeout)
  await tab.click(selector)
} catch (err) {
  console.log("An error occured:", err)
}
// Continue your navigation in this branch
// You should probably do a waitUntilVisible() or waitUntilPresent() here

Before calling click() you should make sure the element you are trying to click on is actually visible or present in the page by using waitUntilVisible() or waitUntilPresent().

Closes the tab in current use.

After close() is called, the tab becomes unusable. All subsequent method calls will throw an exception saying that this specific tab instance has stopped. Lose all references to the instance for it to be garbage-collected and clean cookies and cache used for the whole nick.

Function called when finished (optional).

• err (String): null or a description of what went wrong if something went wrong

try {
  await tab.close()
  // tab can not be used here anymore
  // but you may continue other actions
} catch (err) {
  console.log("Could not close tab:", err)
}

This method is useful when using multiple Nick instances to simulate browsing on multiple tabs. Calling close() is the equivalent of closing a tab.

It can be also useful if you want to iterate on many URLs, the fact that close() clear cache and cookies free a lot of memory.

Calling close() will clear the cookies and cache of the whole nick instantiated before.

Executes inPageFunction in the current page context.

Nick provides you with two separate JavaScript contexts:

1. Where the Nick code runs: this is your script environment, with all your locally declared variables and all your calls to Nick methods
2. Where the page code runs: this is where the page executes jQuery or AngularJS code for example

The evaluate() method allows you to declare a function in your Nick context (1) and executes it in the page context (2). It's like executing code in your browser's inspector tool: you can do anything you want with the page.

In the page context, you have access to all the global variables declared by the page, as well as the DOM (window, document, ...). Any JavaScript libraries included by the page can also be used.

If the page does not include what you want (jQuery or underscore for example), you can inject any JavaScript file with inject() before calling evaluate().

Function to execute in the current page context. argumentObject will be passed as its first argument and a callback as it second argument. argumentObject is an empty plainObject by default. callback is the function to call when finished.

• err (String): null if the function succeeds otherwise put a description of what went wrong
• res (Any): return value of inPageFunction in case of success (this value is serialized to be transferred back to the Nick context — complex object like DOM elements, functions or jQuery objects cannot be returned to the Nick context reliably)

Optional object that will be passed as an argument of inPageFunction (optional). This object is serialized to be transferred to the page context — complex objects like functions or JavaScript modules cannot be passed as argument reliably.

Function called when finished.

• err (String): null or a string describing what went wrong during the evaluation of inPageFunction
• res (Any): return value of inPageFunction in case of success (this value is serialized to be transferred back to the Nick context — complex object like DOM elements, functions or jQuery objects cannot be returned to the Nick context reliably)

const scraper = (arg, done) => {
  // In this case, the current page uses a typical jQuery declared as $
  done(null, $(arg.link).attr("href"))
}
const arg = { link: "#header > a.title" }

try {
  const res = await tab.evaluate(scraper, arg)
  console.log("Scraped this link:", res)
  // Continue your navigation here
} catch (err) {
  console.log("Something went wrong:", err)
}

Because inPageFunction is executed in the current page context, your local variables that have been declared before your evaluate() call will not be accessible. You can, however, transfer variables using the argumentObject parameter.

For this reason, Nick methods won't be available inside evaluate.

When returning data with the callback in the inPageFunction take care to always set the first argument as null if there is no error.

Keep in mind that to transfer inPageFunction and its return value to and from the page context, serialization has to occur. Everything becomes a string at some point. So you cannot return DOM elements or jQuery objects from the page. Moreover, the underlying PhantomJS browser has a bug where serialization of null gives an empty string "" (even in nested objects and arrays). Beware!

Fills a form with the given values and optionally submits it.

Inputs are referenced by their name attribute.

CSS selector targeting what form to fill. It should point to a form tag. Make sure the target form is visible or present by calling waitUntilVisible() or waitUntilPresent() beforehand.

An object containing the data you want to enter in the form. Keys must correspond to the inputs' name attribute. This method supports single select fields in the same way as normal input fields. For select fields allowing multiple selections, supply an array of values to match against.

• submit (Boolean): Whether or not to submit the form after filling it (false by default).

Function called when finished.

• err (String): null or a string describing what went wrong when filling the form

const selector = "#contact-form"
const inputs = {
  "subject": "I am watching you",
  "content": "So be careful.",
  "civility": "Mr",
  "name": "Chuck Norris",
  "email": "[email protected]",
  "cc": true,
  "attachment": "roundhousekick.doc" // file taken from your agent's disk
}

try {
  await tab.waitUntilVisible(selector, 5000)
  await tab.fill(selector, inputs, { submit: true })
  console.log("Form sent!")
  // Continue your navigation in this branch
  // You should probably do a waitUntilVisible() or waitUntilPresent() here
} catch (err) {
  console.log("Form not found:", err)
}

<form action="/contact" id="contact-form" enctype="multipart/form-data">
  <input type="text" name="subject"/>
  <textearea name="content"></textearea>
  <input type="radio" name="civility" value="Mr"/> Mr
  <input type="radio" name="civility" value="Mrs"/> Mrs
  <input type="text" name="name"/>
  <input type="email" name="email"/>
  <input type="file" name="attachment"/>
  <input type="checkbox" name="cc"/> Receive a copy
  <input type="submit"/>
</form>

Returns the current page content as a string.

Function called when finished (optional).

• err (String): null or a description of what went wrong if something went wrong
• content (String): the full HTML content of the current webpage.

try {
  const content = await tab.getContent()
  // content contains the content of the current webpage
} catch (err) {
  console.log("Could not get the content of the page:", err)
}

When the current page is a dynamic JavaScript powered HTML page, getContent() will return a snapshot of the current state of the DOM and not the initial source code.

Returns the current page URL as a string.

Function called when finished (optional).

• err (String): null or a description of what went wrong if something went wrong
• url (String): the full URL of the current page.

try {
  const url = await tab.getUrl()
  console.log("The url of the page is", url)
  // You can use the variable url and continue your actions
} catch (err) {
  console.log("Could not get the current url:", err)
}

The URL you get will be URL-decoded.

Injects a script in the current DOM page context.

The script can be stored locally on disk or on a remote server.

Path to a local or remote script.

Function called when finished (optional).

• err (String): null or a description of what went wrong if something went wrong

const urlOrPath = "https://code.jquery.com/jquery-3.2.1.min.js"

try {
  await tab.inject(urlOrPath)
  console.log("Jquery script inserted!")
  //You may now use tab.evaluate() and use jQuery functions
} catch (err) {
  console.log("Could not inject jQuery:", err)
}

Checks for a list of selectors CSS selectors if they are present in the DOM and return a boolean: true if the selectors are present and false in the contrary.

What to look for in the DOM. Can be an array of CSS selectors (array of strings) or a single CSS selector (string).

When selectors is an array, this optional argument lets you choose how to wait for the CSS selectors(optional). If condition is "and" (the default), the method will check for the presence of all CSS selectors. On the other hand, if condition is "or", the method will check for the presence of any CSS selector.

Function called when finished (optional).

• err (String): null or a description of what went wrong if the function fails to check
• visible (Boolean): true if the condition succeeds or false in the contrary

const selectors = ["div.first", "div.second"]

const present = await tab.isPresent(selectors, "or")
if (present) {
  // Either .first or .second is present at this time
} else {
  console.log("Elements aren't present")
}

Checks for a list of selectors CSS selectors if they are visible in the page and return a boolean: true if the selectors are visible and false in the contrary.

What to check for. Can be an array of CSS selectors (array of strings) or a single CSS selector (string).

When selectors is an array, this optional argument lets you choose how to wait for the CSS selectors (optional). If condition is "and" (the default), the method will check for the visibility of all CSS selectors. On the other hand, if condition is "or", the method will check for the visibility of any CSS selector.

Function called when finished (optional).

• err (String): null or a description of what went wrong if the function fails to check
• visible (Boolean): true if the condition succeeds or false in the contrary

const selectors = ["div.first", "div.second"]

const visible = await tab.isVisible(selectors, "or")
if (visible) {
  // Either .first or .second is visible at this time
} else {
  console.log("Elements aren't visible")
}

Sets an event to a JS confirm alert. Executes the function assigned to this variable whenever a confirm dialog is called by window.confirm. The only parameter is the message sent by the dialog, and the function needs to return the user's response as a boolean.

A string containing the message from the confirm dialog.

tab.onConfirm = (message) => {
  console.log("The confirm messsage is", message)
  return true
}

Sets an event to a JS prompt alert. Executes the function assigned to this variable whenever a prompt dialog is called by window.prompt(). The only parameter is the message sent by the dialog, and the function needs to return the user's response as a string.

A string containing the message from the prompt dialog.

tab.onPrompt = (message) => {
  console.log("The prompt message is", message)
  return "Response"
}

Opens the webpage at url.

By default, it's a GET but you can forge any type of HTTP request using the options parameter.

Opening a page will time out after 10 seconds. This can be changed with the resourceTimeout Nick option (see Nick's options). Note: this time out concerns the initial page but not the resources the page requires thereafter.

URL of the page to open. Should begin with http:// or https:// (or file:// to open a page that was previously downloaded to your agent's disk).

Optional request configuration (optional).

Function called when finished (optional).

• err (String): null or a description of what went wrong if something went wrong (typically if there was a network error or timeout)
• httpCode (Number): the received HTTP code or null if there was a network error
• httpStatus (String): text equivalent of the received HTTP code or null if there was a network error
• url (String): the actually opened URL (can be different from the input URL because of 3xx redirects for example) or null if there was a network error

const url = "https://phantombuster.com/"

try {
  const [httpCode, httpStatus] = await tab.open(url)

  if ((httpCode >= 300) || (httpCode < 200)) {
    console.log("The site responded with", httpCode, httpStatus)
  } else {
    console.log("Successfully opened", url, ":", httpCode, httpStatus)
    // Manipulate the page in this branch
    // You should probably do a waitUntilVisible() or waitUntilPresent() here
  }
} catch(err) {
  console.log("Could not open page:", err)
}

{
  method: "post",
  data:   {
    "some param": "some data",
    "another field":  "this is sent in x-www-form-urlencoded format"
  },
  headers: {
    "Accept-Language": "fr,fr-fr;q=0.8,en-us;q=0.5,en;q=0.3"
  }
}

This method will NOT return an error when the received HTTP isn't 200. An error is returned only when a network error happens. It's your job to check for 404s or 500s with httpCode if needed.

Many pages on the web load slowly and unreliably. Many more make numerous aynchronous queries. For these reasons, you should always wait for the DOM elements that interest you after opening a page with waitUntilVisible()or waitUntilPresent().

Takes a screenshot of the current page.

The local path of the screenshot. The format is defined by the file extension. 'image.jpg' will create a JPEG image in the current folder.

Function called when finished (optional).

• err (String): null or a description of what went wrong if something went wrong

const path = "./image.jpg"

try {
  await tab.screenshot(path)
  console.log("Screenshot saved at", path)
  // Your screenshot is available at this path
} catch (err) {
  console.log("Could not take a screenshot:", err)
}

Scrolls to coordinates [x,y] on the page.

The X-axis coordinate in pixels to scroll to (horizontally).

The Y-axis coordinate in pixels to scroll to (vertically).

Function called when finished (optional).

• err (String): null or a description of what went wrong if something went wrong

const x = 1000
const y = 2000

try {
  await tab.scroll(x, y)
  // Your position will be [1000, 2000] in the page now
} catch (err) {
  console.log("Could not scroll to coordinates:", err)
}

scroll() can also be called using scrollTo()

Scrolls to the bottom of the page.

Function called when finished (optional).

• err (String): null or a description of what went wrong if something went wrong

try {
  await tab.scrollToBottom()
  // You are now at the bottom of the page
} catch (err) {
  console.log("An error occured during the scroll to bottom:", err)
}

Writes keys in an <input>, <textarea> or any DOM element with contenteditable="true" in the current page.

A CSS3 or XPath expression that describes the path to DOM elements.

Keys to send to the editable DOM element.

The three options available are:

• reset (Boolean): remove the content of the targeted element before sending key presses.
• keepFocus (Boolean): keep the focus in the editable DOM element after keys have been sent (useful for input with dropdowns).
• modifiers (PlainObject): modifier string concatenated with a + (available modifiers are ctrl, alt, shift, meta and keypad).

Function called when finished(optional).

• err (String): null or a description of what went wrong if something went wrong

const selector = '#message'
const keys = "Boo!"
const options = {
  reset: true,
  keepFocus: false,
  modifiers: {}
}

try {
  await tab.sendKeys(selector, keys, options)
  console.log("Keys sent!")
  // You may continue your actions here
} catch (err) {
  console.log("Could not send keys:", err)
}

Wait for duration milliseconds.

The number of milliseconds to wait for.

Function called when finished (optional).

• err (String): null or a description of what went wrong if something went wrong

This function has nothing to do with the tab you are using, it is pure syntactic sugar to replace Promise.delay() (from Bluebird). It is like waiting in front of your computer after opening a web page.

try {
  await tab.doSomething()
  await tab.wait(10000)
  // After waiting 10 seconds the script continues
  await tab.doSomething()
} catch (err) {
  console.log("An error occured during the execution:", err)
}

Waits for a list of selectors CSS selectors to be present in the DOM. Aborts with an error if the elements have not become present in the DOM after timeout milliseconds.

selectors can be an array of CSS selectors (array of strings) or a single CSS selector (string).

By default, condition is "and" (wait for all CSS selectors) but it can be changed to "or" (wait for any CSS selector).

What to wait for. Can be an array of CSS selectors (array of strings) or a single CSS selector (string).

Maximum number of milliseconds to wait for, by default it is set to 5000(optional). callback will be called with an error if the elements have not become present after timeout milliseconds.

When selectors is an array, this optional argument lets you choose how to wait for the CSS selectors(optional). If condition is "and" (the default), the method will wait for all CSS selectors. On the other hand, if condition is "or", the method will wait for any CSS selector.

Function called when finished(optional).

• err (String): null or a description of what went wrong if the CSS selectors were not present after timeout milliseconds
• selector (String):
  • In case of success (err is null):
    • If condition was "and" then selector is null because all CSS selectors are present
    • If condition was "or" then selector is one of the present CSS selectors of the given array
  • In case of failure (err is not null):
    • If condition was "and" then selector is one of the non-present CSS selectors of the given array
    • If condition was "or" then selector is null because none of the CSS selectors are present

const selectors = "#header > h1.big-title"
const pageTimeout = 5000

try {
  await tab.waitUntilPresent(selectors, pageTimeout)
  // The element is present in the DOM
} catch(err) {
  console.log("Oh no! Even after 5s, the element was still not present. ", err)
}

Waits for a list of selectors CSS selectors to be visible. Aborts with an error if the elements have not become visible after timeout milliseconds.

selectors can be an array of CSS selectors (array of strings) or a single CSS selector (string).

By default, condition is "and" (wait for all CSS selectors) but it can be changed to "or" (wait for any CSS selector).

What to wait for. Can be an array of CSS selectors (array of strings) or a single CSS selector (string).

Maximum number of milliseconds to wait for, by default it is set to 5000(optional). callback will be called with an error if the elements have not become visible after timeout milliseconds.

When selectors is an array, this optional argument lets you choose how to wait for the CSS selectors(optional). If condition is "and" (the default), the method will wait for all CSS selectors. On the other hand, if condition is "or", the method will wait for any CSS selector.

Function called when finished(optional).

• err (String): null or a description of what went wrong if the CSS selectors were not visible after timeout milliseconds
• selector (String):
  • In case of success (err is null):
    • If condition was "and" then selector is null because all CSS selectors are visible
    • If condition was "or" then selector is one of the visible CSS selectors of the given array
  • In case of failure (err is not null):
    • If condition was "and" then selector is one of the non-visible CSS selectors of the given array
    • If condition was "or" then selector is null because none of the CSS selectors are visible

const selectors = "#header > h1.big-title"
const pageTimeout = 5000

try {
  await tab.waitUntilVisible(selectors, pageTimeout)
  // Manipulate the element here
  // for example with a click() or evaluate()
} catch(err) {
  console.log("Oh no! Even after 5s, the element was still not visible:", err)
}

const selectors = ["#header > h1", "img.product-image"]
const pageTimeout = 6000

try {
  await tab.waitUntilVisible(selectors, pageTimeout)
  // Manipulate the element here
  // for example with a click() or evaluate()
} catch(err) {
  console.log("Oh no! Even after 6s, at least one of the element was still not visible:", err)
}

var selectors = ["section.footer", "section.header"]
var pageTimeout = 7000

try {
  const selector = await tab.waitUntilVisible(selectors, pageTimeout)
  console.log("This element is visible: " + selector)
  // Manipulate the element here
  // For example with a click() or evaluate()
} catch(err) {
  console.log("Oh no! Even after 7s, all the elements were still not visible. " + err)
  // in this case, the callback does not return which element is not visible
  // because ALL the elements are not visible
}

Waits for a list of selectors CSS selectors to become non-present in the DOM. Aborts with an error if the elements are still present in the DOM after timeout milliseconds.

selectors can be an array of CSS selectors (array of strings) or a single CSS selector (string).

By default, condition is "and" (wait for all CSS selectors) but it can be changed to "or" (wait for any CSS selector).

What to wait for. Can be an array of CSS selectors (array of strings) or a single CSS selector (string).

The maximum number of milliseconds to wait for, by default it is set to 5000 (optional). callback will be called with an error if the elements are still present after timeout milliseconds.

When selectors is an array, this optional argument lets you choose how to wait for the CSS selectors (optional). If condition is "and" (the default), the method will wait for all CSS selectors. On the other hand, if condition is "or", the method will wait for any CSS selector.

Function called when finished (optional).

• err (String): null or a description of what went wrong if the CSS selectors were still present after timeout milliseconds
• selector (String):
  • In case of success (err is null):
    • If condition was "and" then selector is null because none of the CSS selectors are present
    • If condition was "or" then selector is one of the non-present CSS selectors of the given array
  • In case of failure (err is not null):
    • If condition was "and" then selector is one of the still present CSS selectors of the given array
    • If condition was "or" then selector is null because all of the CSS selectors are still present

const selectors = "#header > h1.big-title"
const pageTimeout = 5000

try {
  await tab.waitWhilePresent(selectors, pageTimeout)
  // The selector has succesfully become non-present
} catch(err) {
  console.log("Oh no! Even after 5s, the element was still present:", err)
}

Waits for a list of selectors CSS selectors to become non-visible. Aborts with an error if the elements are still visible after timeout milliseconds.

selectors can be an array of CSS selectors (array of strings) or a single CSS selector (string).

By default, condition is "and" (wait for all CSS selectors) but it can be changed to "or" (wait for any CSS selector).

What to wait for. Can be an array of CSS selectors (array of strings) or a single CSS selector (string).

The maximum number of milliseconds to wait for, by default it is set to 5000 (optional). callback will be called with an error if the elements are still visible after timeout milliseconds.

When selectors is an array, this optional argument lets you choose how to wait for the CSS selectors(optional). If condition is "and" (the default), the method will wait for all CSS selectors. On the other hand, if condition is "or", the method will wait for any CSS selector.

Function called when finished(optional).

• err (String): null or a description of what went wrong if the CSS selectors were still visible after timeout milliseconds
• selector (String):
  • In case of success (err is null):
    • If condition was "and" then selector is null because none of the CSS selectors are visible
    • If condition was "or" then selector is one of the non-visible CSS selectors of the given array
  • In case of failure (err is not null):
    • If condition was "and" then selector is one of the still visible CSS selectors of the given array
    • If condition was "or" then selector is null because all of the CSS selectors are still visible

const selectors = "#header > h1.big-title"
const pageTimeout = 5000

try {
  await tab.waitWhileVisible(selectors, pageTimeout)
  // The selector has succesfully become non-visible
} catch(err) {
  console.log("Oh no! Even after 5s, the element was still visible:", err)
}