Use the replace attribute to avoid Composer dependency conflicts
The following tutorial column will introduce you to the method of using the replace attribute to avoid dependency conflicts in Composer. I hope it will be helpful to friends in need! The Composer documentation provides two basic examples. I'll try to explain:
List the packages that were replaced by this package. This way, you can fork a package and publish it under a different name with your own version number, and packages that require the original package can continue to use your forked package because it replaces the original package.
Assume your software usesother/packageoriginal/library
and
, which themselves require original/library
. Now you think
original/library
needs to integrate new features, but the maintainers don't agree with your suggestion to be implemented in their package. So you decide to fork the library under the name
and mark it as a new release. Back to the software. Of course, it should start using the
better/library
package, so use that instead, but
still requires original/library
- code duplication! How do you make that package use your better/library
instead of original/library
? Instead of forking it and just modifying composer.json (you're still compatible with original/library
so it should work)? You need to add the replace keyword in
composer.json
:
"replace": { "original/library":"1.0.2" }
Now Composer knows that when resolving the dependency of "other/package", any changes from "better" /library" packages are as good as "original/library".
Same rule, just a slightly different perspective: Bringing in the framework's components is a good way to go for any other component that needs some functionality. However, if you need a complete framework in your software, and another library requires a component of that framework, the framework'sreplace
declaration saves Composer from having to install that single component twice because it's already included in in a complete frame.
Note: placeholders in replacement versions are generally bad
In my original answer, I suggested: "replace": {
"original/library":"1.*"
}
library is still active and declares that it can be replaced Any version
1*,, even if you don't update anything internally - it won't be done, but if you don't do any work, your old code will never implement the new functionality of the original library, But the replacement content illustrates exactly that. So, essentially: avoid using wildcard versions in replacement versions! If you use them, you are making statements about the future that you cannot know or predict (unless you have control over original/library
, but even then be very careful). Be sure to use
that you know and can completely reimplement. Original address: https://stackoverflow.com/questions/18882201/how-does-the-replace-property-work-with-composer
The above is the detailed content of Use the replace attribute to avoid Composer dependency conflicts. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











When developing an e-commerce website, I encountered a difficult problem: how to provide users with personalized product recommendations. Initially, I tried some simple recommendation algorithms, but the results were not ideal, and user satisfaction was also affected. In order to improve the accuracy and efficiency of the recommendation system, I decided to adopt a more professional solution. Finally, I installed andres-montanez/recommendations-bundle through Composer, which not only solved my problem, but also greatly improved the performance of the recommendation system. You can learn composer through the following address:

Laravel is a PHP framework for easy building of web applications. It provides a range of powerful features including: Installation: Install the Laravel CLI globally with Composer and create applications in the project directory. Routing: Define the relationship between the URL and the handler in routes/web.php. View: Create a view in resources/views to render the application's interface. Database Integration: Provides out-of-the-box integration with databases such as MySQL and uses migration to create and modify tables. Model and Controller: The model represents the database entity and the controller processes HTTP requests.

When developing websites using CraftCMS, you often encounter resource file caching problems, especially when you frequently update CSS and JavaScript files, old versions of files may still be cached by the browser, causing users to not see the latest changes in time. This problem not only affects the user experience, but also increases the difficulty of development and debugging. Recently, I encountered similar troubles in my project, and after some exploration, I found the plugin wiejeben/craft-laravel-mix, which perfectly solved my caching problem.

Article summary: This article provides detailed step-by-step instructions to guide readers on how to easily install the Laravel framework. Laravel is a powerful PHP framework that speeds up the development process of web applications. This tutorial covers the installation process from system requirements to configuring databases and setting up routing. By following these steps, readers can quickly and efficiently lay a solid foundation for their Laravel project.

The Laravel framework has built-in methods to easily view its version number to meet the different needs of developers. This article will explore these methods, including using the Composer command line tool, accessing .env files, or obtaining version information through PHP code. These methods are essential for maintaining and managing versioning of Laravel applications.

VprocesserazrabotkiveB-enclosed, Мнепришлостольностьсясзадачейтерациигооглапидляпапакробоглесхетсigootrive. LEAVALLYSUMBALLANCEFRIABLANCEFAUMDOPTOMATIFICATION, ČtookazaLovnetakProsto, Kakaožidal.Posenesko

When developing an e-commerce website using Thelia, I encountered a tricky problem: MySQL mode is not set properly, causing some features to not function properly. After some exploration, I found a module called TheliaMySQLModesChecker, which is able to automatically fix the MySQL pattern required by Thelia, completely solving my troubles.

I'm having a tricky problem when doing a mail marketing campaign: how to efficiently create and send mail in HTML format. The traditional approach is to write code manually and send emails using an SMTP server, but this is not only time consuming, but also error-prone. After trying multiple solutions, I discovered DUWA.io, a simple and easy-to-use RESTAPI that helps me create and send HTML mail quickly. To further simplify the development process, I decided to use Composer to install and manage DUWA.io's PHP library - captaindoe/duwa.
