Pipe stdin to Phantom.JS and console messages to stdout
npm install -g phantomic
Phantomic does not include PhantomJS itself. Make sure the
executable is in your
PATH or specify with
Usage: phantomic [options] [file]Options:--debug Launch the WebKit debugger in a browser--port <num> Explicit port binding for temporary web server. Ifno port is specified, a random free port is used.--phantomjs <path> Use specified phantomjs binary--web-security <bool> Enables PhantomJS web security and forbidscross-domain XHR (default is true)--brout Assume brout is part of the JS--ignore-ssl-errors <bool> Tell PhantomJS to ignore SSL certificate errorswhen network requests are made (default is false)
Pipe any script to phantomic:
phantomic < ./test.js
Opening a file:
If you are using phantomic from a Makefile with a local install, you will have to include it in the PATH:
BIN = ./node_modules/.binPATH := $(BIN):$(PATH)test:browserify ./test.js | phantomic
debugger; statement somewhere and run:
phantomic --debug < ./test.js
This will open the WebKit inspector in your browser.
By default, phantomic will report an error if anything was logged to
console.error. Program termination is detected by observing delays in the
event queue and the last log statement that was received.
To make exit detection more reliable, brout can be used. If brout is part
of the given script, run phantomic with
--brout to install handlers for the
exit events. Also make sure
process.exit(code) is called.
You can use phantomic from your own node scripts like this:
var phantomic = require'phantomic';phantomicprocessstdindebug : falseport : 0brout : false'web-security': false'ignore-ssl-errors': trueprocessexitcode;pipeprocessstdout;