Closed mikebronner closed 9 years ago
The problem is I'm currently trying to execute composer init
directly in the newly-created project directory. The way I do that (using symfony/process
) causes problems, though. Not sure how we can use composer init
and simply forward input/output to/from that process.
Could you hide the output of composer init
, i.e. by suppressing errors in the call using @
-- given that the errors are false positives?
The errors above actually aren't from composer init
. They're a result of init not being executed properly (because it doesn't get any input, such as a package name).
Try now, we're getting there. =)
When creating packages, I get the following error outputs:
I'm not sure if this is affecting the result or not, but it does create folders and files within them. I have it running on Laravel Homestead 2.x vm, which is running on Ubuntu 14.04. Will be happy to help troubleshoot if needed.