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 11 Support #216

Open
ahmedK03 opened this issue Dec 19, 2024 · 1 comment
Open

Laravel 11 Support #216

ahmedK03 opened this issue Dec 19, 2024 · 1 comment

Comments

@ahmedK03
Copy link

No description provided.

@moosecodes
Copy link

moosecodes commented Jan 31, 2025

same issue.

composer.json:

"require": {
        "php": "^8.2",
        "inertiajs/inertia-laravel": "^1.0",
        "laravel/framework": "^11.31",
        "laravel/jetstream": "^5.3",
        "laravel/sanctum": "^4.0",
        "laravel/telescope": "^5.3",
        "laravel/tinker": "^2.9",
        "stevebauman/location": "^7.4",
        "tightenco/ziggy": "^2.0"
    },
    "require-dev": {
        "fakerphp/faker": "^1.23",
        "laravel/pail": "^1.1",
        "laravel/pint": "^1.13",
        "laravel/sail": "^1.26",
        "mockery/mockery": "^1.6",
        "nunomaduro/collision": "^8.1",
        "phpunit/phpunit": "^11.0.1"
    },

Console output after running: composer require jenssegers/agent:

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

  Problem 1
    - Root composer.json requires jenssegers/agent * -> satisfiable by jenssegers/agent[v1.0.0, v2.0.0, ..., v2.6.4].
    - jenssegers/agent v1.0.0 requires illuminate/support ~4.0 -> found illuminate/support[v4.0.0, ..., v4.2.17] but these were not loaded, likely because it conflicts with another require.
    - jenssegers/agent[v2.0.0, ..., v2.1.2] require illuminate/support 4.* -> found illuminate/support[v4.0.0, ..., v4.2.17] but these were not loaded, likely because it conflicts with another require.
    - jenssegers/agent[v2.1.3, ..., v2.5.2] require illuminate/support ^4.0|^5.0 -> found illuminate/support[v4.0.0, ..., v4.2.17, v5.0.0, ..., v5.8.36] 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.45] but the package is fixed to 4.8.09 (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.

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 jenssegers/agent:*" to figure out if any version is installable, or "composer require jenssegers/agent:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

Does anyone know if is it advisable to use the --with-all-dependencies option?

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

2 participants