Why use aliases?
The following column of composer tutorial will introduce to you the reasons for using branch aliases. I hope it will be helpful to friends in need!
Why use aliases?
When you use a version control system repository, you can only get a comparable version from branches that look like versions, such as 2.0 or 2.0.x. For the master branch, you only get one dev-master version. For the bugfix branch, you will get the dev-bugfix version.
If your master branch is used to mark the 1.0 development process, such as 1.0.1, 1.0.2, 1.0.3, etc., packages that depend on your library may need 1.0.*.
If someone wants to use the latest dev-master, they will encounter a problem: some packages may require 1.0.*, so these two will cause conflicts, because dev-master does not Matches 1.0.*.
Based on the above, aliases appear.
Branch Alias
The dev-master branch is one of the main VCS repositories. It's common that some people will want the latest major development version. Therefore, Composer allows you to alias the dev-master branch to the 1.0.x-dev version. It is done by specifying the branch-alias field under extra in composer.json:
{ "extra": { "branch-alias": { "dev-master": "1.0.x-dev" } } }
If the alias is a non-comparable version (such as dev-develop), you must prefix the branch name with dev- . You can also add aliases (i.e. starting with a number and ending with .x-dev) for comparable versions, but only as more specific versions. For example, 1.x-dev can be aliased as 1.2.x-dev.
The alias must be a comparable development version, and branch-alias must appear on the branch it refers to. For dev-master you need to commit it on the master branch.
So a lot of people need 1.0.* now and he will be happy to install dev-master .
To use a branch alias, you must own the repository for the aliased package. If you want to add an alias to a third-party package without maintaining a fork of it, use inline aliases, as described below.
Requires inline aliases
Branch aliases are useful for major lines of development. But in order to use them, you need to control the source repository, and changes need to be committed to version control.
It's not very interesting when you want to try a bug fix for a library that is a dependency of your local project.
So you can alias packages in the require and require-dev fields. Suppose you find a bug in the monolog/monolog package. You clone Monolog on GitHub and fix the problem in a branch called bugfix. Now you want to install this version of monolog in your local project.
You are using symfony/monolog-bundle, which requires monolog/monolog version 1.*. Therefore, you need to use dev-bugfix to match this constraint.
Add this to your project's root composer.json:
{ "repositories": [ { "type": "vcs", "url": "https://github.com/you/monolog" } ], "require": { "symfony/monolog-bundle": "2.0", "monolog/monolog": "dev-bugfix as 1.0.x-dev" } }
This will get the version of monolog/monolog's dev-bugfix from your Github and alias it to 1.0.x -dev.
Note: Inline aliasing is a feature only available to the root user. If a package with an inline alias is required, use the alias (right side of as ) as a version constraint. The left part of as is discarded. So if A requires B and B requires the monolog/monolog version dev-bugfix for 1.0.x-dev , installing A will also make B require 1.0.x-dev as well, which may exist as a branch alias or the actual 1.0 branch. If not, you'll have to alias inline again in A 's composer.json .
Note: Using inline aliases should be avoided, especially for published packages/libraries. If you find a bug, try merging your fix upstream, this will help avoid problems for users of your package.
For more composer technical articles, please visit the composer command usage tutorial column!
The above is the detailed content of Why use aliases?. 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





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.

I had a tough problem when working on a project with a large number of Doctrine entities: Every time the entity is serialized and deserialized, the performance becomes very inefficient, resulting in a significant increase in system response time. I've tried multiple optimization methods, but it doesn't work well. Fortunately, by using sidus/doctrine-serializer-bundle, I successfully solved this problem, significantly improving the performance of the project.

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.

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:

To install Laravel, follow these steps in sequence: Install Composer (for macOS/Linux and Windows) Install Laravel Installer Create a new project Start Service Access Application (URL: http://127.0.0.1:8000) Set up the database connection (if required)

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.

When developing an e-commerce platform, it is crucial to choose the right framework and tools. Recently, when I was trying to build a feature-rich e-commerce website, I encountered a difficult problem: how to quickly build a scalable and fully functional e-commerce platform. I tried multiple solutions and ended up choosing Fecmall's advanced project template (fecmall/fbbcbase-app-advanced). By using Composer, this process becomes very simple and efficient. Composer can be learned through the following address: Learning address
