codebright

The Primers 21
1 "require": {
2 "xmen/gambit": "dev-master"
3 },
4 "require-dev": {
5 "codeception/codeception": "1.6.0.3"
6 }
The codeception/codeception package will now only be installed if we use the --dev switch with
Composer. There will be more on this topic in the installation and usage section.
As you can see above, the require-dev section uses exactly the same format as the require section.
In fact, there are other sections which use the same format. Let’s have a quick look at what’s
available.
1 "conflict": {
2 "marvel/spiderman": "1.0.0"
3 }
The conflict section contains a list of packages that would not work happily alongside our package.
Composer will not let you install these packages side by side.
1 "replace": {
2 "xmen/gambit": "1.0.0"
3 }
The replace section informs you that this package can be used as a replacement for another package.
This is useful for packages that have been forked from another, but provide the same functionality.
1 "provide": {
2 "xmen/gambit": "1.0.0"
3 }
This section indicates packages that have been provided within the codebase of your package. If the
Gambit packages source was included within our main package then it would be of little use to install
it again. Use this section to let Composer know which packages have been embedded within your
primary package. Remember, you need not list your package dependencies here. Anything found in
require doesn’t count.