Closed TheTooz closed 2 years ago
@fuglyducky So why do you want to run npm init playwright
on CI? This should never be the case unless you do some meta-automation!
@aslushnikov, that is a good question. Our test nodes do not have node installed in their images so we need to install node, and then install playwright. To avoid issues where we have an old version of node and/or playwright in our images, I was just wondering if there is a way to completely automate the installation and configuration process.
@fuglyducky usually this is solved by package-lock.json
. It will pin all the packages to proper versions and install them and their dependencies, giving you reproducible builds!
Since my rotation is over, let me close this for now. If you do think that package-lock.json
is not suitable for some reason for you, please feel free to open a new issue! :)
I do need to accomplish this by specifying JavaScript at installation command for silent install instead of the default TypeScript for my dockerized setup
Unless I completely missed something on the documentation, I cannot install playwright without some manual input. Namely choosing typescript vs javascript, et al.
To make the lives of our CI team easier, and not require continual updates to our machine images, we would like to be able to install playwright on the fly without any user intervention.