Support Laravel 10?

[ErickZH]

This package support laravel 10 with php 8.1 ?

[ash-jc-allen]

Hey @ErickZH! As far as I can see, this package should support running on Laravel 10 with PHP 8.1 🙂

[ErickZH]

Hi @ash-jc-allen
I am trying to install this package in Laravel 10 with php 8.1 but I am getting this error:

composer require ashallendesign/short-url
./composer.json has been updated
Running composer update ashallendesign/short-url
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - ashallendesign/short-url[dev-tuskcode/master, dev-master, dev-analysis-jlY1PJ, dev-patch-1, v7.4.0, ..., v7.8.2] require jenssegers/agent ^2.6 -> satisfiable by jenssegers/agent[v2.6.0, ..., v2.6.4].
    - ashallendesign/short-url[v0.0.1, v1.0.0, ..., v1.2.1, v2.0.0, ..., v2.3.1, v3.0.0, v4.0.0, ..., v4.1.1] require php ^7.2 -> your php version (8.1.26) does not satisfy that requirement.
    - ashallendesign/short-url[v4.2.0, ..., v4.3.0, v5.0.0, ..., v5.2.0] require illuminate/container ^6.0|^7.0|^8.0 -> found illuminate/container[v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.
    - ashallendesign/short-url[v6.0.0, ..., v6.2.0] require illuminate/container ^8.0 -> found illuminate/container[v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.
    - ashallendesign/short-url[dev-feature-eloquent-factories, v6.3.0, v7.0.0, ..., v7.3.0] require illuminate/container ^8.0|^9.0 -> found illuminate/container[v8.0.0, ..., 8.x-dev, v9.0.0-beta.1, ..., 9.x-dev] but these were not loaded, likely because it conflicts with another require.
    - jenssegers/agent[v2.6.0, ..., v2.6.4] require mobiledetect/mobiledetectlib ^2.7.6 -> found mobiledetect/mobiledetectlib[2.7.6, ..., 2.8.x-dev] but the package is fixed to 4.8.05 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - Root composer.json requires ashallendesign/short-url * -> satisfiable by ashallendesign/short-url[dev-feature-eloquent-factories, dev-tuskcode/master, dev-master, dev-analysis-jlY1PJ, dev-patch-1, v0.0.1, v1.0.0, v1.1.0, v1.2.0, v1.2.1, v2.0.0, ..., v2.3.1, v3.0.0, v4.0.0, ..., v4.3.0, v5.0.0, v5.1.0, v5.2.0, v6.0.0, v6.1.0, v6.2.0, v6.3.0, v7.0.0, ..., v7.8.2, 9999999-dev].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require ashallendesign/short-url:*" to figure out if any version is installable, or "composer require ashallendesign/short-url:^2.1" if you know which you need.

Also try the installation with this command:

composer require ashallendesign/short-url:^7.8.2 -W
./composer.json has been updated
Running composer update ashallendesign/short-url --with-all-dependencies
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - jenssegers/agent[v2.6.0, ..., v2.6.4] require mobiledetect/mobiledetectlib ^2.7.6 -> found mobiledetect/mobiledetectlib[2.7.6, ..., 2.8.x-dev] but these were not loaded, likely because it conflicts with another require.
    - ashallendesign/short-url v7.8.2 requires jenssegers/agent ^2.6 -> satisfiable by jenssegers/agent[v2.6.0, ..., v2.6.4].
    - Root composer.json requires ashallendesign/short-url ^7.8.2 -> satisfiable by ashallendesign/short-url[v7.8.2].

[ash-jc-allen]

Would it be possible for you to share your composer.json file, please?

And out of interest, are you using Laravel Jetstream in this project? I'm wondering whether this issue is related to #227? 🙂

[ErickZH]

Yes, I'm using Laravel Jetstream :(

[ash-jc-allen]

I've been trying to come up with a nice solution so that Jetstream and this package can work on the same project. But I've been really struggling to think of anything without having to remove some features of the package :(