composer-php

What means “locked at” <tag> in composer

风流意气都作罢 提交于 2021-01-19 06:32:54
问题 Trying to perform a composer update <package> but getting the following error: The requested package <package> (locked at <tag>, required as dev-<branchXY>) is satisfiable by <package>[<tag>] but these conflict with your requirements or minimum-stability. Meanwhile, the tag <tag> exists as a string only in my composer.lock file, of which I thought it was only modified by composer update but not read. What does 'locked at' mean in this context and how do I solve the issue? composer why-not

What means “locked at” <tag> in composer

一笑奈何 提交于 2021-01-19 06:31:53
问题 Trying to perform a composer update <package> but getting the following error: The requested package <package> (locked at <tag>, required as dev-<branchXY>) is satisfiable by <package>[<tag>] but these conflict with your requirements or minimum-stability. Meanwhile, the tag <tag> exists as a string only in my composer.lock file, of which I thought it was only modified by composer update but not read. What does 'locked at' mean in this context and how do I solve the issue? composer why-not

What means “locked at” <tag> in composer

夙愿已清 提交于 2021-01-19 06:29:38
问题 Trying to perform a composer update <package> but getting the following error: The requested package <package> (locked at <tag>, required as dev-<branchXY>) is satisfiable by <package>[<tag>] but these conflict with your requirements or minimum-stability. Meanwhile, the tag <tag> exists as a string only in my composer.lock file, of which I thought it was only modified by composer update but not read. What does 'locked at' mean in this context and how do I solve the issue? composer why-not

What means “locked at” <tag> in composer

若如初见. 提交于 2021-01-19 06:29:06
问题 Trying to perform a composer update <package> but getting the following error: The requested package <package> (locked at <tag>, required as dev-<branchXY>) is satisfiable by <package>[<tag>] but these conflict with your requirements or minimum-stability. Meanwhile, the tag <tag> exists as a string only in my composer.lock file, of which I thought it was only modified by composer update but not read. What does 'locked at' mean in this context and how do I solve the issue? composer why-not

Run composer dump-autoload from controller in laravel 5

这一生的挚爱 提交于 2021-01-15 18:39:05
问题 I want to run composer dump-autoload without shell command in controller. In laravel 4 I use Artisan::call('dump-autoload'); but in laravel 5 this command not work. 回答1: Artisan is not wrapper for composer . Composer itself brings the composer command to control itself. Currently there is no way to call composer commands in a proper way from Artisan - not even with creating your own Artisan command with php artisan make:console CommandName . Unless you don't want to use PHPs exec or system ,

Run composer dump-autoload from controller in laravel 5

生来就可爱ヽ(ⅴ<●) 提交于 2021-01-15 18:36:52
问题 I want to run composer dump-autoload without shell command in controller. In laravel 4 I use Artisan::call('dump-autoload'); but in laravel 5 this command not work. 回答1: Artisan is not wrapper for composer . Composer itself brings the composer command to control itself. Currently there is no way to call composer commands in a proper way from Artisan - not even with creating your own Artisan command with php artisan make:console CommandName . Unless you don't want to use PHPs exec or system ,

Install Laravel using Composer

十年热恋 提交于 2021-01-14 09:06:57
问题 I'm trying to install Laravel using Composer , but after running the following command composer create-project laravel/laravel cmsLaravel 5.2 pointing to my c/xampp/htddocs directory, I get the error below: C:\xampp\htdocs\laravelCMS\bootstrap/../vendor/autoload.php): failed to open stream: No such file or directory in C:\xampp\htdocs\laravelCMS\bootstrap\autoload.php on line 17 回答1: To install Laravel using composer, all you need to do is to run in your terminal is: composer create-project -

Downgrading from bootstrap 4 to 3 in yii2

China☆狼群 提交于 2021-01-07 01:23:51
问题 I was currently working on a project using the yii2 framework. I wanted to try out using bootstrap 4.0 with my project and added "yiisoft/yii2-bootstrap": "~2.1.0@dev" to my composer.json file and ran composer update . This successfully installed bootstrap 4.0.0 in the project but when I started to browse my project to see what was affected I realized that the yii\bootstrap\Modal component was not working. Because of this, I want to revert my project back to using bootstrap 3 and changed my

Downgrading from bootstrap 4 to 3 in yii2

Deadly 提交于 2021-01-07 01:21:41
问题 I was currently working on a project using the yii2 framework. I wanted to try out using bootstrap 4.0 with my project and added "yiisoft/yii2-bootstrap": "~2.1.0@dev" to my composer.json file and ran composer update . This successfully installed bootstrap 4.0.0 in the project but when I started to browse my project to see what was affected I realized that the yii\bootstrap\Modal component was not working. Because of this, I want to revert my project back to using bootstrap 3 and changed my

Error: You made a reference to a non-existent script @php artisan package:discover

旧城冷巷雨未停 提交于 2020-12-30 19:17:11
问题 I am getting error at running composer dump-autoload at laravel project composer dump-autoload Generating autoload files > Illuminate\Foundation\ComposerScripts::postAutoloadDump You made a reference to a non-existent script @php artisan package:discover Then executing php artisan package:discover returns Discovered Package: barryvdh/laravel-ide-helper Discovered Package: cartalyst/sentinel Discovered Package: laravelcollective/html Discovered Package: laracasts/generators Package manifest