Nightmare is a high-level browser automation library.
The goal is to expose just a few simple methods, and have an API that feels synchronous for each block of scripting, rather than deeply nested callbacks. It's designed for automating tasks across sites that don't have APIs.
Under the covers it uses Electron, which is similar to PhantomJS but faster and more modern.
Daydream is a complementary chrome extension built by @stevenmiller888 that generates Nightmare scripts for you while you browse.
Many thanks to @matthewmueller for his help on Nightmare.
Let's search on Yahoo:
var Nightmare = require('nightmare');
yield Nightmare()
.goto('http://yahoo.com')
.type('input[title="Search"]', 'github nightmare')
.click('.searchsubmit');
Or, let's run some mocha tests:
var Nightmare = require('nightmare');
var expect = require('chai').expect; // jshint ignore:line
describe('test yahoo search results', function() {
it('should find the nightmare github link first', function*() {
var nightmare = Nightmare()
var breadcrumb = yield nightmare
.goto('http://yahoo.com')
.type('input[title="Search"]', 'github nightmare')
.click('.searchsubmit')
.wait('.url.breadcrumb')
.evaluate(function () {
return document.querySelector('.url.breadcrumb').innerText;
});
expect(breadcrumb).to.equal('github.com');
});
});
You can see examples of every function in the tests here.
Please note that the examples are using the mocha-generators package for Mocha, which enables the support for generators.
Create a new instance that can navigate around the web. The available options are documented here.
Set the useragent
used by electron.
Complete any queue operations, disconnect and close the electron process.
Load the page at url
.
Go back to the previous page.
Go forward to the next page.
Refresh the current page.
Clicks the selector
element once.
Enters the text
provided into the selector
element.
Toggles the selector
checkbox element.
Changes the selector
dropdown element to the option with attribute [value=option
]
Scrolls the page to desired position. top
and left
are always relative to the top left corner of the document.
Inject a local file
onto the current page. The file type
must be either js
or css
.
Invokes fn
on the page with arg1, arg2,...
. All the args
are optional. On completion it returns the return value of fn
. Useful for extracting information from the page. Here's an example:
var selector = 'h1';
var text = yield nightmare
.evaluate(function (selector) {
// now we're executing inside the browser scope.
return document.querySelector(selector).innerText;
}, selector); // <-- that's how you pass parameters from Node scope to browser scope
Wait for ms
milliseconds e.g. .wait(5000)
Wait until the element selector
is present e.g. .wait('#pay-button')
Wait until the fn
evaluated on the page returns true
.
Returns whether the selector exists or not on the page.
Returns whether the selector is visible or not
Capture page events with the callback. You have to call .on()
before calling .goto()
. Supported events are documented here.
Saves a screenshot of the current page to the specified path
. Useful for debugging. The output is always a png
. You can optionally provide a clip rect as documented here.
Saves a PDF with A4 size pages of the current page to the specified path
. Options are here.
Returns the title of the current page.
Returns the url of the current page.
Nightmare is a Node.js module, so you'll need to have Node.js installed. Then you just need to npm install
the module:
$ npm install --save nightmare
Nightmare is a node module that can be used in a Node.js script or module. Here's a simple script to open a web page:
var Nightmare = require('../nightmare');
var vo = require('vo');
vo(run)(function(err, result) {
if (err) throw err;
});
function *run() {
var nightmare = Nightmare();
var title = yield nightmare
.goto('http://cnn.com')
.evaluate(function() {
return document.title;
});
console.log(title);
yield nightmare.end();
}
If you save this as cnn.js
, you can run it on the command line like this:
npm install vo nightmare
node --harmony cnn.js
There are three good ways to get more information about what's happening inside the headless browser:
- Use the
DEBUG=*
flag described below. - Pass
{ show: true }
to the nightmare constructor to have it create a visible, rendered window that you can watch what's happening. - Listen for specific events.
To run the same file with debugging output, run it like this DEBUG=nightmare node --harmony cnn.js
(on Windows use set DEBUG=nightmare & node cnn.js
).
This will print out some additional information about what's going on:
nightmare queueing action "goto" +0ms
nightmare queueing action "evaluate" +4ms
Breaking News, U.S., World, Weather, Entertainment & Video News - CNN.com
Automated tests for nightmare itself are run using Mocha and Chai, both of which will be installed via npm install
. To run nightmare's tests, just run make test
.
When the tests are done, you'll see something like this:
make test
․․․․․․․․․․․․․․․․․․
18 passing (1m)
WWWWWW||WWWWWW
W W W||W W W
||
( OO )__________
/ | \
/o o| MIT \
\___/||_||__||_|| *
|| || || ||
_||_|| _||_||
(__|__|(__|__|
Copyright (c) 2015 Segment.io, Inc. friends@segment.com
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.