Composer vs. Yarn

I do highly recommend it whenever you have some PHP projects, especially if you need to have reusable modules that you want to share across teams. With a good branching an tagging strategy, you can go a long way in making your developers' life easier. They will only need to work on the modules that are of interest of them, and not have to touch the whole codebase.

Also, it's quite necessary if you are planning to use community PHP modules, as the vast majority of them is distributed, and versionned via packagist.org, and thus via composer.

Incentivized

There is really no real reason why not to use Yarn today. It's much faster than npm, and you will need a dependency management system anyway. The only thing that might be missing is the fact that it doesn't come natively with NodeJS, and you have to install it yourself. I'd like to see the NodeJS ecosystem include Yarn by default.

Incentivized

• Controlling dependencies
• Fast dependency resolver
• Easy to use dependency injection

Incentivized

• Package management
• Speed of download compared to npm
• Moduel version control

Incentivized

• Sometimes a bit slow, but v2 made a lot of improvements on that
• If everything is modular, setting up a local dev environment is a bit trickier than having everything in the same repo
• Might be hard to adopt with some frameworks which have not fully embraced it, like Wordpress

Incentivized

• Rarely, some server connection error appear, while npm works alright.
• Sometimes, deleting the whole vendor directory is the best solution to solve weird issues.
• You still might need npm to install Yarn.

Incentivized

If you're familiar with npm or Yarn, you'll feel right at home with composer. The work in pretty much the same way. You can use a composer.json file in your repo to reference specific version of public community modules, and enterprise internal ones. You can also hook some scripts that you would want to execute, like for testing, building your code ...

Incentivized

Compared to npm, Yarn is a clear winner here. npm does not look to be getting any improvements recently. And it's much much slower to run when installing project dependencies. This has a clear impact on the developer productivity but also makes deployments slower. So Yarn is still a much superior choice.

Incentivized

• Composer only has had positive impacts in our business. It saves a lot of time and resource in order to develop a software.

Incentivized

• Deployments happen much faster.
• Building and testing our apps is much more streamlined and efficient.
• Makes it easier to write reusable code.

Incentivized