使用 AWS EB cli 部署 laravel 5:UnexpectedValueException - 无效的版本字符串 [英] Deploying laravel 5 with AWS EB cli: UnexpectedValueException - Invalid version string
本文介绍了使用 AWS EB cli 部署 laravel 5:UnexpectedValueException - 无效的版本字符串的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
所以我正准备几个月来第一次部署一些更改,但我得到了这个错误:
So I was just about to deploy some changes for the first time in some months, and I get this error back:
[UnexpectedValueException]
Could not parse version constraint ^1.2.2: Invalid version string "^1.2.2"
经过一番挖掘,我在 composer.lock 文件中找到了这一行:
After some digging, I found the line in my composer.lock file:
{
"_readme": [
...
],
"hash": "NotTellingYou",
"packages": [
{
...
},
....
"require": {
"nikic/php-parser": "^1.2.2",
"php": ">=5.3.3",
"symfony/console": "~2.1",
"symfony/filesystem": "~2.1",
"symfony/finder": "~2.1"
},
但是 ehhh... 那么如何使字符串正确"呢?我知道最新版本是 1.3,但我可以更改它吗?运行composer update
时不应该是自动的吗?
But ehhh... How do I make the string the "correct" then? I know the newest version is 1.3, but is it okay for me to change that? Shouldn't it be automatic when running composer update
?
推荐答案
更改 "nikic/php-parser": "^1.2.2"到 "nikic/php-parser": "1.*",
change "nikic/php-parser": "^1.2.2" to "nikic/php-parser": "1.*",
这篇关于使用 AWS EB cli 部署 laravel 5:UnexpectedValueException - 无效的版本字符串的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!
查看全文