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

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

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

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

According to @ULYHPR789, yes.

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