If you have a look at the composer install instructions, basically you have to download the binary and then move it into your bin folder. This means that the name of it is completely arbitrary and while most people probably have named their one and only compose binary “composer” you don’t have to do so. Remember, that Composer is ultimately just a binary on your host machine / inside your VM. How to Install Composer 1 and 2 Simultaneously But not everyone can do this so, if you can’t, read one! What if there was a third option? What if you could use Composer 2 AND Composer 1 that way neither of the “bad” options happen? Well good news! There is a way to do this (and this article is all about how).Ī quick note: ideally, updating to Composer 2 isn’t that hard and I talk about it here. The problem with the above scenario is that neither is a great solution, but something has to be done in order to get the work done. Do you try and force that project to update (not always viable) or do you downgrade to work on that project (not a great answer)? This creates a bit of a conundrum for people (like me) who have already done the update. ![]() Having said that, anytime a new version of something comes out, there are sometimes projects that aren’t able to update to support that new thing for whatever, totally legit reason. And man, let me tell you, I was super excited when Composer 2 dropped last year! I’ve been using it daily ever since. ![]() It can be really exciting when something new comes out.
0 Comments
Leave a Reply. |