MedicOneSystems / MedicOneSystems/livewire-datatables
php 8.1 problem
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 1.2k
- Forks
- 257
- PR merge metrics
- No merged PRs in 30d
Description
Hi, when i run composer require mediconesystems/livewire-datatables in a new Laravel 10 application i get errors:
Problem 1
- mediconesystems/livewire-datatables[v0.0.1, ..., v0.4.3] require php ^7.2.5 -> your php version (8.1.6) does not satisfy that requirement.
- mediconesystems/livewire-datatables[v0.5.0, ..., v0.6.8] require illuminate/support ^7.0|^8.0 -> found illuminate/support[v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27] but these were not loaded, likely because it conflicts with another require.
- mediconesystems/livewire-datatables[v0.7.0, ..., v0.10.0] require illuminate/support ^7.0|^8.0|^9.0 -> found illuminate/support[v7.0.0, ..., v7.30.6, v8.0.0, ..., v8.83.27, v9.0.0, ..., v9.52.15] but these were not loaded, likely because it conflicts with another require.
- mediconesystems/livewire-datatables v0.10.1 requires reedware/laravel-relation-joins ^2.4|^3.0|dev-l10-compatibility -> found reedware/laravel-relation-joins[v2.4.0, v2.4.1, v2.4.2, v3.0.0] but it conflicts with your root composer.json require (4.0).
- Root composer.json requires mediconesystems/livewire-datatables * -> satisfiable by mediconesystems/livewire-datatables[v0.0.1, ..., v0.10.1].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the composer require mediconesystems/livewire-datatables command in a new Laravel 10 application using PHP 8.1.6, then inspect the root composer.json constraints and the reported package conflicts. Done would mean the package can be installed with these versions without the listed dependency-resolution errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- laravel, php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100