codebright

The Primers 17
1 "role": "Genius"
The role option defines the author’s role within the project. For example, developer, designer, or
even sock puppetry artist. If you can’t think of something accurate then put something funny.
That’s all you need to describe your package, now let’s look at something more interesting.
Dependency management!
Dependency Management
You have a box that will contain the X-Men. Only there aren’t a lot of mutants in that box yet. To
build a great superhero team (application) you will need to enlist the support of other mutants (3rd
party dependencies). Let’s have a look at how Composer will help us accomplish this.
1 {
2 "name": "marvel/xmen",
3 "description": "Mutants saving the world for people who hate them."
4 "keywords": ["mutant", "superhero", "bald", "guy"],
5 "homepage": "http://marvel.com/xmen",
6 "time": "1963-09-01",
7 "license": "MIT",
8 "authors": [
9 {
10 "name": "Stan Lee",
11 "email": "stan@marvel.com",
12 "homepage": "http://marvel.com",
13 "role": "Genius"
14 }
15 ],
16 "require": {
17
18 }
19 }
We now have a new section within our composer.json called require. This will be used to list our
dependenc… mutants. From now on I’ll be omitting the rest of the configuration, and just showing
the require block to shorten the examples. Make sure you know where it really lives though!
We know that the X-Men will depend on:
• Wolverine
• Cyclops