Giovanni Bassi

I'm having the same problem. It does not fail but the cache is invalidated and rebuilt because of different node versions coming from the matrix. Example: https://github.com/giggio/node-chromedriver/runs/5439981596?check_suite_focus=true

Thanks, @celluj34. I migrated to AutoMoqCore.

Sure, just download any tool which Chocolatey. I use Sysinternals: https://chocolatey.org/packages/sysinternals If you don't want to install Chocolatey, just download "Process Explorer" directly (https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer) and add it to your path...

I'm having the same issue mentioned in #121, `terminalizer render demo` simply exits without any messages. I'm also on WSL2. @takanotume24 were you able to solve the issue?

So maybe when WSL2 has desktop support it'll work. I was able to render on Windows.

Just downgrade `postcss-loader` to `1.2.1` and add `postcss-load-config` version `1.0.0` to your package.json, and you are good to go, until they fix things on `bootstrap-loader`.

Chromedriver is a binary executable not a Node.js script, and this package does not control it, it only allows you to install it and start the process. I'm not sure...

Ok, that makes sense. A PR is welcome but it must not break the existing api.

Yes, during the download phase, but not at the end, as the name is used for caching. Something would have to be built around it, because at the end we...

Not yet, the code to start Chromedriver is really simple, see: https://github.com/giggio/node-chromedriver/blob/1e97332826aced66fe1b3368e50d8b279c7b3bf9/lib/chromedriver.js#L5-L11 We can't change `start` method signature without breaking existing users, but we could add another method. How about...