Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Bug] Installation through composer fails - likely due to big package size

See original GitHub issue

Bug report

What I did

composer install or composer update or composer require.

What I expected to happen

Should install/update backpack/crud library.

What happened

Installation stuck for very long time on (for e.g.) Downloading backpack/crud (4.1.54), then it fails. It says it tried to download from dist but failed then tries to download from source but fails again. I fail to understand why download from dist is failing in the first place.

What I’ve already tried to fix it

I’ve followed instructions in the other similar issues:

Cleared cache and tried again: composer clearcache.
Preferred source: composer require backpack/crud --prefer-source
I’ve also installed an arbitrary php package to see if the problem is with composer or my internet connection, but no error occurred there.
I also tried to install backpack in an empty directory composer require "backpack/crud", all other libraries/dependencies gets installed but still fails on installing backpack/crud with same error as above. 😦

Software Versions

Laravel v8.32.1 Composer 2.0.10 PHP 7.3.11 git 2.30.1.windows.1

Thanks, any help much appreciated. xD

Issue Analytics

State:
Created 2 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

karandatwani92commented, Aug 31, 2022

@tabacitu I’m facing same issue from three-four days, delaying everything. I’m trying the above fix but it’s not appropriate as it keeps one waiting for so long. This issue is particularly happening to CRUD package only. Other Backpack Packages are downloading smoothly.

1reaction

tabacitucommented, Sep 28, 2021

Personally I’ve a hunch that it’s due to backpack’s huge filesize (~36MB) and/or some incompatibility with composer’s (or php’s) default configs, evidenced by the fact that other php packages were being successfully installed on the same machine.

Might be. Since that’s the only thing that’s different - all other packages get served by Packagist & Github too.

We plan to eliminate the CSS & JS dependencies from the package in the next version. That’ll make it <1 MB so hopefully nobody’s going to get this kind of issue 🤞

I’m going to close this issue since you found a solution, and it’ll get fixed as a sideffect of the next version changes - we have 3-4 issues about that already.

Thanks for posting about this @Saif-XI-Coderz . Cheers!

Top Results From Across the Web

Troubleshooting - Composer

Try clearing Composer's cache by running composer clear-cache . Ensure you're installing vendors straight from your composer.json via rm -rf vendor && composer...

Solved: Package Big Sur installer with Composer issue

Solved: Hello, I downloaded and got the Big Sur installer which is 12.21 GB. When I try to package it with Composer, the...

Composer Update failed -- out of memory - Stack Overflow

Composer may sometimes fail on some commands with this message: PHP Fatal error: Allowed memory size of XXXXXX bytes exhausted <...> Or in...

Common bugs and issues — Anaconda 38.14 documentation

These issues are related to the content that is installed on the target system. Non-fatal POSTIN scriptlet failure¶. Issue. The package installation fails...

Chapter 10. Known issues Red Hat Enterprise Linux 8

The authselect-compat package is required by the auth and authconfig Kickstart commands during installation. Without this package, the installation fails if ...