I want to generate a Symfony application which can be compatible with PHP version up to 7.4.22. On my local machine, PHP version is 8.0.2 but on the hosting is 7.4.22. Symfony application is generated from local machine using standard composer command I look over create-project arguments to see if I could add some constrains but none seems to be
Tag: composer-php
Can we add subdirectory manually after the psr-4 composer namespace path?
I have different versions of files which are stored in separate subfolders inside a main folder. I intend to use subfolder based on a dynamically determined value of $ver. Can I create a psr-4 composer namespace for the main folder and then add to it the $ver for subfolders as needed. I tried following but its showing errors. File Structure:
Data not passed correctly from Laravel controller to blade view **ONLY IN PRODUCTION**
I have recently encountered a problem with my Laravel application when deployed to Heroku. Just to note, this has been working just fine in production until very recently. The above snippets still work as intended in dev using Laravel Valet; However, in production, the $isFollowing variable is always returned to the view as bool(false) regardless of whether the data shows
Composer dependency not met for large package [closed]
Closed. This question needs details or clarity. It is not currently accepting answers. Want to improve this question? Add details and clarify the problem by editing this post. Closed last year. Improve this question I am needing to install a package into my Laravel project. I am using the latest version of Laravel (8), It comes preinstalled with; When I
“php artisan myCommand” handling the post-install-cmd event returned with error code 1
I creaded a console command that will setup the database automatically based on user input and I added that command in post-install-cmd but when i run the composer install command it return error code 1. If i run the command manually like php artisan setupDB it work, I dont know what is the issue. May be I am adding my
Composer install fail on TFS Server
We are running a Team Foundation Server (on premises) and as part of a build process it runs composer to install dependancies. Sometime in the last week this process has started failing and I cannot figure out why. Here is the console output from a failed run: Here is part of the output from a successful run about a month
Unable to change file mode on bin: Operation not permitted
I’m trying to install Composer globally on Mac OS. I tried to move the composer.phar file by using this command in Terminal as instructed in the Getting Started section: I get this error: When I try create the directory it says the operation is not permitted: I even tried to navigate to the “bin” directory and it says: I’ve enabled
How to fix Illegal offset type in Drupal/mystore/vendor/composer/composer/src/Composer/DependencyResolver/Pool.php:61
I’m very new to Drupal and trying to install it with composer. My composer install went well, but now, each time I try to do something, I get this error in the console : I get the feeling that this may be a compatibility issue ? Here is my composer.json : I have absolutely no idea how to fix this,
Composer outdated command doesn’t show latest versions [closed]
Closed. This question needs details or clarity. It is not currently accepting answers. Want to improve this question? Add details and clarify the problem by editing this post. Closed last year. Improve this question I am using Composer version 2.0.8, with Docker. When I use the command composer outdated -f json inside a composer project, the field “latest”, giving the
why I get spatie/laravel-cors[1.2.0, …, 1.2.2] require illuminate/support 5.5.*|5.6.* when i run composer require spatie/laravel-cors
Facing this issue After I Upgraded project from Laravel 6 to Laravel 7. I actually could not upgrade laravel/framework package from 6 to 7 due to some other error of spatie/laravel-cors but than I removed spatie/laravel-cors and upgraded laravel/framework, after upgrading it wont install again. here is full error: Answer On the github page of the Spatie/Laravel-cors you can find