Is NickJS going to change the steps of 'npm install nickjs' installation in future?

[MehdiRaash]

I just paste npm install nickjs and I received some warnings.

Shouldn't a chromium browser gets downloaded as part of nickJS installation instead of manually pointing chromium executable path?

Thanks for the library.

[paps]

NickJS supports multiple drivers, at the moment CasperJS+PhantomJS and Chrome. I'm not a fan of downloading 2 full headless browsers for every npm install.

How would you do it? We're open to suggestions :)

[MehdiRaash]

As we all know, consumers of these kind of libraries are more expert than other developers or at least they are more curious(within ambition), which we can say, they can begin to work at the end of the day if everything is not ready, but in comparison to new libraries like Puppeteer which it installs a proper chromium while npm package installation, it seems like it would be more friendlier whether to ask for a browser download.

[adelriosantiago]

+1, it is not a good idea to tell "oh install this and that headless browser" to the developer. Or maybe two projects could be created nickjs-browsers-bundled and nickjs alone.

[serverlessguru]

We are trying to upgrade our NodeJS8.10 application which uses NickJS, however we don't have a compatible chrome binary.

We were using, https://github.com/adieuadieu/serverless-chrome/tree/master/packages/lambda, but they don't have NodeJS10.x+ chrome binaries.

We are now looking at using, https://github.com/alixaxel/chrome-aws-lambda. Does anyone know if these chrome binaries would be compatible?

The application will be running on Amazon Linux 2, using NodeJS10.x or NodeJS12.x, as NodeJS8.10 is end-of-life.

Does anyone have any recommendations?