indus / ncc Goto Github PK

No errors are logged, it just opens Chrome window and there is blank canvas of default size, it seems like Chrome doesn't receive any commands from Node.

On Raspbian buster, ncc is able to launch chromium and it claims to be running the devtools API on the specified port, but I get connection failed messages, even after upping the retry limit and waiting a while. I also needed to specify
export LIGHTHOUSE_CHROMIUM_PATH=/usr/bin/chromium-browser to get it to work without code changes.

Possible fix might be to try using the proper chrome-launcher npm package https://www.npmjs.com/package/chrome-launcher

Could you list one or more use cases for this tool? What can we do with such a Canvas object in Node?

OS X 10.12.4 (16E195)
Chrome 58.0.3029.110 (64-bit)
node v6.10.0

ChromeLauncher created /var/folders/dc/_638b5l12vv8ltt22j1nvvym0000gn/T/ncc.XXXXXXX.YinKOGZj
ChromeLauncher Chrome running with pid 30961 on port 9222.
ChromeLauncher Waiting for browser.
ChromeLauncher Waiting for browser...
ChromeLauncher Waiting for browser.....
ChromeLauncher Waiting for browser.....
[ncc] chrome started
[ncc] connecting [retry 1/9]
[ncc] connecting [retry 2/9]
[ncc] connecting [retry 3/9]
[ncc] connecting [retry 4/9]
[ncc] connecting [retry 5/9]
[ncc] connecting [retry 6/9]
[ncc] connecting [retry 7/9]
[ncc] connecting [retry 8/9]
[ncc] connecting [retry 9/9]
[ncc] connection failed

a lot of issues in node-canvas deal with installation problems:

Automattic/node-canvas#919
Automattic/node-canvas#913
Automattic/node-canvas#911
Automattic/node-canvas#905
Automattic/node-canvas#901
Automattic/node-canvas#890
Automattic/node-canvas#871
Automattic/node-canvas#854
Automattic/node-canvas#852
Automattic/node-canvas#796
Automattic/node-canvas#788
Automattic/node-canvas#779
Automattic/node-canvas#771
Automattic/node-canvas#768
Automattic/node-canvas#755
Automattic/node-canvas#752
Automattic/node-canvas#751
Automattic/node-canvas#745
Automattic/node-canvas#731

With ncc you just need an installation of chrome(-ium) on your system and everything should be fine.

toDataURL() works great but the overhead of decoding base64 makes it inefficient for my purposes (rendering to an LED panel). I looked at supporting toBlob() but it uses a callback, unlike toDataURL(), and I can't see how to do this with rdp().