---
title: "Discussion on \"Efficiently resolving composer.lock merge conflicts\" | Hashnode"
description: "Discussion on \"Efficiently resolving composer.lock merge conflicts\". Efficiently resolving composer.lock git merge conflicts\nWhen working in a team on a PHP project using Composer, you have probably encountered a problem when multiple people added, removed or updated some packages in composer.json and composer.lock on..."
url: "https://hashnode.com/posts/efficiently-resolving-composerlock-merge-conflicts/6504125ad015fbee70e84759"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Efficiently resolving composer.lock merge conflicts](https://blog.bazan.dev/efficiently-resolving-composerlock-merge-conflicts?utm_source=hashnode&utm_medium=feed)

Efficiently resolving composer.lock git merge conflicts When working in a team on a PHP project using Composer, you have probably encountered a problem when multiple people added, removed or updated some packages in composer.json and composer.lock on...

Apr 7, 2021 · 4 min read · blog.bazan.dev  
Read the article

## Written by

[Ion Bazan](https://hashnode.com/@IonBazan)

@IonBazan · Singapore

  
[View profile](https://hashnode.com/@IonBazan)

Lead Software Engineer @ Aspire

I'm a Full Stack Software Developer born in Moldova 🇲🇩, raised in Poland 🇵🇱 and based in Singapore 🇸🇬, who is passionate about good practices 📖, clean code 🧹, containerized environments 🐋 and good pizza 🍕.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
