carlo

carlo copied to clipboard

Remote devices in Chrome:  Remote devices in Carlo:  When I remote debug webView using chrome, I have to open `chrome://inspect/#devices`, then click the `inspect` link of one page,...

kimown

carlo will not launch on win10

2

Accoding to some bug/feature in puppeteer, carlo/puppeteer will not launch on win10 sometimes. see: https://github.com/GoogleChrome/puppeteer/issues/3186 **here is how to fix I found:** when launch puppeteer, add an option `ignoreDefaultArgs: ['--disable-extensions'],`...

mu-yu

Carlo won't load a next.js site. This is error message in the console: Failed to load resource: net::ERR_BLOCKED_BY_CLIENT /_next/static/4sXxrLKhlqKMGukbOt5t1/pages/_app.js:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT /_next/static/runtime/webpack-a79426b5e11f0ba5879d.js:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT...

ericbets

Using an AZERTY keyboard on OSX, when typing `cmd` + `a` it is mapped as `cmd` + `q` and closes the window.

XavierLeTohic

hot reload?

3

anyway to see my changes immediately after modifying a source file? right now I have to manually shut it down, write a fix, run carlo

whatsdis

Sometimes carlo launches into the wrong window when using "--auto-open-devtools-for-tabs" launch arg

2

When debugging, it is useful to automatically launch devtools for the window, using the "--auto-open-devtools-for-tabs" flag. Example main.js: ``` const carlo = require('carlo'); (async () => { const app =...

gadamsgh

Notification.onclick() doesn't seem to work

2

```js const permission = await Notification.requestPermission(); if (permission === "granted") { new Notification('some-title').onclick = (ev) => { console.log(ev) } } ```

VandeurenGlenn

Question: Why doesn't Carlo automatically install Chrome in the home directory?

9

Hey. So this is a really great initiative and I'm following the progress closely. I was wondering if it would be a good idea for carlo apps to ship with...

kitze

Allow configuration of where the RPC content script is read from via rpcContentScriptDir

1

This allows the RPC content script to be arbitrary read from any directory, rather than the default `__dirname + '../rpc/rpc.js`. This is important in situations where `node_modules` may be inaccessible...

nessup

app.exit never resolves

3

It seems `app.exit()` never resolves. Repro: ```js const carlo = require('carlo'); (async () => { const app = await carlo.launch(); console.log('launched'); console.log('exiting...'); await app.exit(); console.log('exited'); // this never logs })();...

laggingreflex