view release on metacpan or  search on metacpan

README.mkdn  view on Meta::CPAN

    Specify the path to the PhantomJS executable.

    The default is `phantomjs` as found via `$ENV{PATH}`.
    You can also provide this information from the outside
    by setting `$ENV{PHANTOMJS_EXE}`.

- **phantomjs\_arg**

    Additional command line arguments to `phantomjs`.  (phantomjs -h)

        phantomjs_arg => ["--proxy=$ENV{HTTP_PROXY}"]

- **launch\_ghostdriver**

    Filename of the `ghostdriver` Javascript code
    to launch. The default is the file distributed with this module.

        launch_ghostdriver => "devel/my/ghostdriver/main.js",

- **launch\_arg**

lib/WWW/Mechanize/PhantomJS.pm  view on Meta::CPAN

Specify the path to the PhantomJS executable.

The default is C<phantomjs> as found via C<$ENV{PATH}>.
You can also provide this information from the outside
by setting C<$ENV{PHANTOMJS_EXE}>.

=item B<phantomjs_arg>

Additional command line arguments to C<phantomjs>.  (phantomjs -h)

  phantomjs_arg => ["--proxy=$ENV{HTTP_PROXY}"]

=item B<launch_ghostdriver>

Filename of the C<ghostdriver> Javascript code
to launch. The default is the file distributed with this module.

  launch_ghostdriver => "devel/my/ghostdriver/main.js",

=item B<launch_arg>

t/helper.pm  view on Meta::CPAN

package # hide from CPAN indexer
    t::helper;
use strict;
use Test::More;
use File::Glob qw(bsd_glob);
use Config '%Config';
use File::Spec;
use Time::HiRes qw( time sleep );
use Carp qw(croak);

delete $ENV{HTTP_PROXY};
delete $ENV{HTTPS_PROXY};

sub browser_instances {
    my ($filter) = @_;
    $filter ||= qr/^/;
    my @instances;
    # default PhantomJS instance
    my ($default)=
        map { my $exe= File::Spec->catfile($_,"phantomjs$Config{_exe}");
              -x $exe ? $exe : ()