Re: https://github.com/sindresorhus/pageres/pull/212/files#r41089180

@kevva @SamVerschueren Comment here before doing it so we don't have any conflict ;)

The current WebKit in PhantomJS is ancient. We should upgrade to PhantomJS 2 as soon as it is available. Hopefully within this month or next.

https://groups.google.com/forum/#!topic/phantomjs/z6Xy1f0Xqhc

This is currently blocked by the PhantomJS 2.0 release being broken... We have to wait for the phantomjs module to upgrade: https://github.com/Medium/phantomjs/issues/288

Hello! Cool tool, I'm excited about using it. I installed it and PhantomJS (via macports) and get this result:

$ pageres http://www.nationalgeographic.com 320x480 1024x768 1366x768

/usr/local/lib/node_modules/pageres/cli.js:91 throw err; ^ Error: }

    };

    // 15. If the [[Class]] internal property of Target is "Function", then
    //     a. Let L be the length property of Target minus the length of A.
    //     b. Set the length own property of F to either 0 or L, whichever is
    //       larger.
    // 16. Else set the length own property of F to 0.

    var boundLength = Math.max(0, target.length - args.length);

    // 17. Set the attributes of the length own property of F to the values
    //   specified in 15.3.5.1.
    var boundArgs = [];
    for (var i = 0; i < boundLength; i++) {
        boundArgs.push("$" + i);
    }

    // XXX Build a dynamic function with desired amount of arguments is the only
    // way to set the length property of a function.
    // In environments where Content Security Policies enabled (Chrome extensions,
    // for ex.) all use of eval or Function costructor throws an exception.

I have already followed the other issues ( e.g. https://github.com/sindresorhus/pageres/issues/152 ) but both API and cli are not rendering webfonts, both widh font-face and link inclusion. I have not phantomjs installed globally, I re-installed multiple times pageres and made sure it was the right version. Any thought?

Any URL above 104 characters makes pageres choke immediately (before even sending any web request it seems):

$ pageres "https://tools.wmflabs.org/wikivoyage/w/poimap2.php?lat=42.333333&lon=12.283333&zoom=13&layer=O&lang=en&name=Fabrica_di_Roma" 1680x1080

events.js:74
        throw TypeError('Uncaught, unspecified "error" event.');
              ^
TypeError: Uncaught, unspecified "error" event.
    at TypeError (<anonymous>)
    at EventEmitter.emit (events.js:74:15)
    at cleanupSync (/usr/local/lib/node_modules/pageres/node_modules/fs-write-stream-atomic/index.js:46:42)
    at WriteStream.emit (/usr/local/lib/node_modules/pageres/node_modules/fs-write-stream-atomic/index.js:53:12)
    at WriteStream.<anonymous> (evalmachine.<anonymous>:1660:12)
    at OpenReq.Req.done (/usr/local/lib/node_modules/pageres/node_modules/fs-write-stream-atomic/node_modules/graceful-fs/graceful-fs.js:141:5)
    at OpenReq.done (/usr/local/lib/node_modules/pageres/node_modules/fs-write-stream-atomic/node_modules/graceful-fs/graceful-fs.js:61:22)
    at Object.oncomplete (evalmachine.<anonymous>:107:15)

pageres 1.1.0 Ubuntu 2014.04 nodejs v0.10.25 http_parser: '1.0' node: '0.10.25' v8: '3.14.5.9' ares: '1.10.0' uv: '0.10.23' zlib: '1.2.8' modules: '11' openssl: '1.0.1f' npm: '1.3.10'

Difference between URLs of respectively 105 and 104 characters:

$ pageres "http://123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123.com" 1680x1080

events.js:74
        throw TypeError('Uncaught, unspecified "error" event.');
              ^
TypeError: Uncaught, unspecified "error" event.
    at TypeError (<anonymous>)
    at EventEmitter.emit (events.js:74:15)
    at cleanupSync (/usr/local/lib/node_modules/pageres/node_modules/fs-write-stream-atomic/index.js:46:42)
    at WriteStream.emit (/usr/local/lib/node_modules/pageres/node_modules/fs-write-stream-atomic/index.js:53:12)
    at WriteStream.<anonymous> (evalmachine.<anonymous>:1660:12)
    at OpenReq.Req.done (/usr/local/lib/node_modules/pageres/node_modules/fs-write-stream-atomic/node_modules/graceful-fs/graceful-fs.js:141:5)
    at OpenReq.done (/usr/local/lib/node_modules/pageres/node_modules/fs-write-stream-atomic/node_modules/graceful-fs/graceful-fs.js:61:22)
    at Object.oncomplete (evalmachine.<anonymous>:107:15)

$ pageres "http://12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012.com" 1680x1080
Couldn't load url: http://12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012.com

Running the example command …

❯ pageres todomvc.com yeoman.io 1366x768 1600x900

Gives this error:

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: spawn EACCES
    at errnoException (child_process.js:980:11)
    at Process.ChildProcess._handle.onexit (child_process.js:771:34)

And …

❯ sudo !!

… gives the following warning:

You are not allowed to run this app with root permissions.
If running without sudo doesn't work, you can either fix your permission problems or change where npm stores global packages by putting ~/npm/bin in your PATH and running:
npm config set prefix ~/npm

… in which I did the latter part, i.e. adding ~/npm/bin in my $home (had to create the directory) and include it in my $PATH.

Still the same error. Any clues?

Versions of binaries

node 0.10.24 npm 1.3.21 pageres 0.2.3 phantomjs 1.9.7 (The one that came as a dependency when installing pageres)

OS

Mac OS X 10.9.1

So I tried this using a data URI but it didn't work due to protocolify prepending http:// before the URL. This fixes that.

Will also need to be fixed in the CLI.

Fixes #254.

First Thank you very much for this.

I used last time but it dose not display google font.

<link rel='stylesheet' type='text/css' href='http://fonts.googleapis.com/css?family=Open+Sans:400,800,300'>

but result image dose not display Open Sans font.. If you know this already I am so sorry.

Now that we have coverage checking we should get it to 100%.

https://coveralls.io/r/sindresorhus/pageres

We just run the following and dig into the report:

npm run coverage -- --reporter=lcov

Pull requests to improve this would be much appreciated :rabbit:

• [x] Document CLI more than just a --help dump. Do a tutorial or something
• [x] Document the keywords that can be used instead of sizes. https://github.com/kevva/viewport-list/issues/2

Feedback welcome on what else.

Using a .JSON file (see cookies.json), you can attach cookies to the phantom page request. This will allow you to capture pages that are behind a login wall.

An issue exists for this at: https://github.com/sindresorhus/pageres/issues/41

hi, when i want to connect on resource with self signer certificate, i receive error:

C:\Users\user>pageres --overwrite -d 10 --format=png --filename=image123.png "https://127.0.0.1
file:///C:/Users/user/AppData/Roaming/npm/node_modules/pageres-cli/node_modules/puppeteer-core/lib/esm/puppeteer/common/Frame.js:210
                    ? new Error(`${response.errorText} at ${url}`)
                      ^

Error: net::ERR_CERT_AUTHORITY_INVALID at https://127.0.0.1
    at navigate (file:///C:/Users/user/AppData/Roaming/npm/node_modules/pageres-cli/node_modules/puppeteer-core/lib/esm/puppeteer/common/Frame.js:210:23)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Frame.goto (file:///C:/Users/user/AppData/Roaming/npm/node_modules/pageres-cli/node_modules/puppeteer-core/lib/esm/puppeteer/common/Frame.js:180:21)
    at async CDPPage.goto (file:///C:/Users/user/AppData/Roaming/npm/node_modules/pageres-cli/node_modules/puppeteer-core/lib/esm/puppeteer/common/Page.js:437:16)
    at async internalCaptureWebsiteCore (file:///C:/Users/user/AppData/Roaming/npm/node_modules/pageres-cli/node_modules/capture-website/index.js:282:2)
    at async internalCaptureWebsite (file:///C:/Users/user/AppData/Roaming/npm/node_modules/pageres-cli/node_modules/capture-website/index.js:162:10)
    at async Pageres.create (file:///C:/Users/user/AppData/Roaming/npm/node_modules/pageres-cli/node_modules/pageres/dist/index.js:226:28)
    at async file:///C:/Users/user/AppData/Roaming/npm/node_modules/pageres-cli/node_modules/p-map/index.js:141:20

Node.js v18.12.1

how to fix it?

Hey, It's an excellent project for capturing screenshots. but it works only on the local machines. I set it up on vercel, and it can't take screenshots and doesn't give any error. it just skips the step. Can you help with that?

I take screenshots of more than 10,000 websites. But sometimes in a way that I don't understand, the program crashes in this way and my program does not continue. Is there a solution for this? At the very least, I want the program to continue.

I am using pageres-cli and I found that the default timeout of 60 seconds as described in readme is not working if the command is run from PowerShell (default with new Windows Terminal). However with cmd.exe command completed within a few seconds with error as expected.

For eg,. run following command in PowerShell and the command will never complete, at least in my machine.

pageres https://www.google.com --overwrite --filename='google' --verbose --selector='.any-class'

pageres-cli 0.6.0 Windows 10

Trying to capture a page with a live cam. the page is https://www-cavaliernd-com.filesusr.com/html/269adf_63b45d747777ed5f4d4d231a41b34f81.html but the pic taken is (even when using a 10 sec delay to let the camera load)

This is not an issue (rather a feature request) but I would like to know if there is a way to retrieve the "final" URL of the page Pageres made the screenshot. Many pages have redirects e.g. requesting a screenshot with the url http://sap.com redirects me to https://www.sap.com/. Thanks!