Bạn đang xem: Updating the laravel installer
C:xampphtdocsBigWaveMediadavinkit>php artisan migrate "error": "type": "Exception", "message": "expected color value: failed at `.clearfix;` C:\xampp\htdocs\BigWaveMedia\davinkit\app\start/../../public/less/style.less on line 102", "file": "C:\xampp\htdocs\davinkit\vendor\leafo\lessphp\lessc.inc.php", "line": 3258 C:xampphtdocsBigWaveMediadavinkit>Any ideas at all? Here is a full log http://pastebin.com/y9q4Rc5z
php laravel composer-php
edited Mar 6, 2019 at 10:34
2,81211 gold badge1414 silver badges3131 bronze badges
asked Jul 16, 2014 at 14:07
2,26599 gold badges3737 silver badges6262 bronze badges
| Show 2 more comments
5 Answers 5
Sorted by: Reset to mặc định
Trending sort available
Trending sort Trending sort is based off of the mặc định sorting method — by highest score — but it boosts votes that have happened recently, helping lớn surface more up-to-date answers.
It falls back khổng lồ sorting by highest score if no posts are trending.Switch to lớn Trending sort
Highest score (default) Trending (recent votes count more) Date modified (newest first) Date created (oldest first)
When you run composer update, composer generates a file called composer.lock which lists all your packages & the currently installed versions. This allows you lớn later run composer install, which will install the packages listed in that file, recreating the environment that you were last using.
It appears from your log that some of the versions of packages that are listed in your composer.lock tệp tin are no longer available. Thus, when you run composer install, it complains và fails. This is usually no big khuyến mãi - just run composer update & it will attempt lớn build a phối of packages that work together và write a new composer.lock file.
Xem thêm: php datetime function
However, you"re running into a different problem. It appears that, in your composer.json file, the original developer has added some pre- or post- update actions that are failing, specifically a php artisan migrate command. This can be avoided by running the following: composer update --no-scripts
This will run the composer update but will skip over the scripts added khổng lồ the file. You should be able khổng lồ successfully run the update this way.
However, this does not solve the problem long-term. There are two problems:
A migration is for database changes, not random stuff lượt thích compiling assets. Go through the migrations và remove that code from there.
Assets should not be compiled each time you run composer update. Remove that step from the composer.json file.
From what I"ve read, best practice seems to lớn be compiling assets on an as-needed basis during development (ie. When you"re making changes to lớn your LESS files - ideally using a tool like gulp.js) and before deployment.