Quick question: ```> PhantomInstaller\Installer::installPhantomJS sh: /data/vendor/bin/phantomjs:

UQ958DA4U

Quick question:

I keep seeing this happening on different projects while running composer install. Is there any way to fix it?

UK5DS29L2

npm install first (or yarn install)

UK5DS29L2

this will install phantomjs

UK5DS29L2

which will allow composer postscripts to execute successfully

Valerii Trots

I would expect that this happens with docker/sdk, right?

UQ958DA4U

Yes

UQ958DA4U

@UK5DS29L2 Thanks for the tip! 'll give it a shot. However, I assumed that this was run through composer and not through npm? the error reporting could be a bit better if it was required to run npm install first.

Valerii Trots

It's about composer, yes.

Valerii Trots

Let me bring here some internal discussions regarding the topic in a minute.

UQ958DA4U

I mean it's not keeping me off doing anything, stuff works but I just found it a bit ... weird.

Valerii Trots

xxx
One more annoying thing:
every time I rundocker/sdk cli composer install -o
PhantomJS is installed
sh: /data/vendor/bin/phantomjs: not found
Caught exception while checking PhantomJS version:
Undefined offset: 0
  - Installing phantomjs (2.1.1): Downloading (100%)      
I tried composer install inside cli - sme issue


Mike Kalinin
Does it have any impact?

xxx
slow comoser install 🙂

Mike Kalinin
It takes 2 seconds for me to install phantom.js…

But anyway we do not need it in docker at all.

So I would consider removing phantom.js from composer post-install.

xxx
but you cannot do this globally, many projects are still using vagrant.
So it should be documented/explained or condiioned

yyy
@Mike Kalinin Am I right that we don’t use PhantomJS in docker environment and for client’s project I can safely remove it from my composer.json to get rid of installing it for every composer install?
It causes a delay during gitlab pipeline run.

Mike Kalinin  [15:46 Uhr]
I am opened for suggestions. How to disable it in some envs?

yyy
Is it useful for this situation
"scripts": {
    "post-install-cmd": [
         "[ $COMPOSER_DEV_MODE -eq 0 ] || <your command>"
    ]
}


<https://stackoverflow.com/questions/13087088/composer-run-scripts-only-in-dev-environment>

What environment variable could be used in this situation, like $COMPOSER_DEV_MODE in this example?


Mike Kalinin
Actually we can use
--no-scripts
for prod-like mode that is actually used in CI.

Mike Kalinin
Good finding with COMPOSER_DEV_MODE

UQ958DA4U

ok, gist is: I can just run --no-scripts in CI?

Valerii Trots

According to @ULYHPR789, yes.

Valerii Trots

Or maybe it's just an assumption on how to fix the problem in future. I'm not sure. 🤔

UK5DS29L2

the problem with phantomjs is that it is often built for node, SOMETIMES repo doesnt' allow you to download some file which is not your fault.

UK5DS29L2

this could be prevented if the docker had the libvips installed so phantomjs can build itself from source

sprymiker

docker/sdk does not need phantomjs in app container, separate container is used for E2E testing.

UK5DS29L2

that's ok, but you could make this not throw errors by modifying the docker image to keep the requirement consistent with docker/non-docker setup

UK5DS29L2

because it doesn't make sense to me to keep separate composer.json files for docker/non-docker

UK5DS29L2

and it doesn't hurt to adjust docker image slightly