Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

laravel 5.8 unable to install #270

Open
yany88 opened this issue Mar 27, 2019 · 11 comments
Open

laravel 5.8 unable to install #270

yany88 opened this issue Mar 27, 2019 · 11 comments

Comments

@yany88
Copy link

yany88 commented Mar 27, 2019

  • symfony/dependency-injection 3.4.x-dev conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.0 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.0-BETA1 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.0-BETA2 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.0-BETA3 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.0-BETA4 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.0-RC1 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.0-RC2 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.1 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.10 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.11 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.12 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.13 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.14 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.15 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.16 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.17 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.18 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.19 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.2 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.20 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.21 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.22 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.23 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.3 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.4 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.5 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.6 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.7 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.8 conflicts with symfony/http-kernel[v4.2.4].
    • symfony/dependency-injection v3.4.9 conflicts with symfony/http-kernel[v4.2.4].
    • Installation request for symfony/http-kernel (locked at v4.2.4) -> satisfiable by symfony/http-kernel[v4.2.4].
@ligne13
Copy link

ligne13 commented May 14, 2019

Same issue here

@mikeburton220
Copy link

Same

@goowikns
Copy link

Got the same issue, any news on this? It's already been a few months.

@neokyuubi
Copy link

I'm having the same issue with laravel 5.7.

@elephantux
Copy link

This may help:

composer require "jonnyw/php-phantomjs:@dev"

@neokyuubi
Copy link

neokyuubi commented Jul 15, 2019

This may help:

composer require "jonnyw/php-phantomjs:@dev"

I have used that dev version before but it creates a new whole problems of incompatibility. and you have to use an older pahntomJs and also some tweaks to set its path.
So finally i just switched to nesk/puphpeteer

Thanks.

@allanvb
Copy link

allanvb commented Sep 14, 2019

Same issue, does anyone found solution ? (except dev version)

@neokyuubi
Copy link

neokyuubi commented Sep 15, 2019

@allanvb I found an other package that lets you use the same syntax as "jonnnnyw/php-phantomjs" (last update was 2018-04-03).
It's "josh/laravel-phantomjs" (which is more recent, last update was 2019-03-27) i didn't check but maybe it's a fork.

Anyways, after installing it you can either use the syntax in the "jonnnnyw/php-phantomjs" documentation page or stick with the way that "josh/laravel-phantomjs" gives us.

here's an example assuming that your browser is in the bin folder"/bin/phantomjs" of your root application :

$url = 'www.website.com';
$client = \JonnyW\PhantomJs\Client::getInstance();
$client->getEngine()->setPath( base_path().'/bin/phantomjs');
$request_ = $client->getMessageFactory()->createRequest($url, 'GET');
$response_ = $client->getMessageFactory()->createResponse();
$req->addHeader('user-agent', 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_5) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/12.1.1 Safari/605.1.15');
$client->getEngine()->addOption('--load-images=false');
$client->isLazy();
$client->send($request_, $response_);

Ps : I recommend to try it on a fresh installation of Laravel 5.8 before implementing it in your project just in case.

@d2x
Copy link

d2x commented Nov 13, 2019

Remove the vendor directory completely and reinstall
rm -rf vendor
composer install

@dk-jessn
Copy link

dk-jessn commented Dec 10, 2019

Even removing vendor dir completely and reinstall using composer does not work at all times. In production and pre-production we do this on every deploy in general, but it does not fix the issue with a non-working and missing phantomjs file.

I solved it by processing a post-script that copies phantomjs to the vendor/bin folder and made a chmod change on the file to allow read and execution.

@neokyuubi
Copy link

try this : composer require neokyuubi/php-phantomjs:dev-master

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants