A dependency-free parser library for composer.json and composer.lock files.
composer require mcstreetguy/composer-parserI recommend using the provided magic Factory method for parsing:
use MCStreetguy\ComposerParser\Factory as ComposerParser;
$composerJson = ComposerParser::parse('/path/to/composer.json');
$lockfile = ComposerParser::parse('/path/to/composer.lock');Even if this is the easiest way to retrieve an instance, it may be that you for some reason cannot rely on these automations (e.g. if you got a differing filename). In this case you can also call the parse methods directly:
$composerJson = ComposerParser::parseComposerJson('/some/file');
$lockfile = ComposerParser::parseLockfile('/another/file');Please note that ComposerParser will not complain about any missing fields, instead it fills all missing values with default ones to ensure integrity.
During instatiation through the Factory, two exceptions may occur:
try {
$composerJson = ComposerParser::parse('/path/to/composer.json');
} catch (InvalidArgumentException $e) {
// The given file could not be found or is not readable
} catch (RuntimeException $e) {
// The given file contained an invalid JSON string
}If you can not rely on the Factory for any reason, you can also instantiate the class directly.
This is however not recommended and may lead to unexpected behaviour.
use \MCStreetguy\ComposerParse\ComposerJson;
$rawData = file_get_contents('/path/to/composer.json');
$parsedData = json_decode($rawData, true);
$composerJson = new ComposerJson($parsedData);As you can see the constructor needs an array with the parsed json data. This applies to all constructor methods throughout the library.
You can also create sub-components directly.
In this case you have to keep in mind, that their constructors only accept the isolated data from the composer manifest
(e.g. the Author class expects you to pass only the contents of one of the objects in the author-field).
use \MCStreetguy\ComposerParse\Json\Author;
$rawData = file_get_contents('/path/to/composer.json');
$parsedData = json_decode($rawData, true);
$author = new Author($parsedData['authors'][0]);All class instances provide getters for their properties. The structure is directly adapted from the composer.json schema. The corresponding property names of wrapper classes have been converted to camelCase (see the PSR-1 standard for further information).
For any property you can use the provided getter methods.
$license = $composerJson->getLicense();
$version = $composerJson->getVersion();It's also possible to directly access properties. Please note that this is read-only!
$description = $composerJson->description;
$require = $composerJson->require;You may also call empty() or isset() on the class properties.
To check if the whole wrapper is empty (useful for nested classes) there is an isEmpty() method inherited:
if ($composerJson->config->isEmpty()) {
// Do something
}ComposerParser uses some special classes for parts of the json schema.
The PackageMap class is used for the fields require, require-dev, conflict, replace, provide and suggest.
It converts a json structure like this:
{
"require": {
"vendor/package": "^2.3",
"foo/bar": "dev-master"
}
}into an array structure like this:
$require = [
[
"package" => "vendor/package",
"version" => "^2.3"
],
[
"package" => "foo/bar",
"version" => "dev-master"
]
]Additionally it implements the Iterator and ArrayAccess interfaces, thus you may directly access it's contents or put it in a foreach loop:
$require = $composerJson->getRequire();
$fooBar = $require[1];
foreach ($require as $requirement) {
$package = $requirement['package'];
$version = $requirement['version'];
echo "I need $package at version $version!";
}If you for some reason need the original mapped data you can retrieve it as following:
$map = $require->getData();The NamespaceMap is used for the fields autoload.psr-0 and autoload.psr-4.
In fact this class is identical to the PackageMap. The only difference are the map keys:
{
"psr-4": {
"MCStreetguy\\ComposerParser\\": "src/"
}
}$psr4 = [
[
"namespace" => "MCStreetguy\\ComposerParser\\",
"source" => "src/"
]
]By default, the library tries to load your global configuration file, if there is any. It follows the location rules for the composer home directory as defined in the documentation. If there is no readable global configuration file present, this step is silently skipped.
Just as composer itself, the following precedence rule applies to global configuration files:
In case global configuration matches local configuration, the local configuration in the project's composer.json always wins. (source: https://getcomposer.org/doc/03-cli.md#composer-home-config-json)
You may suppress this behaviour by passing true as second parameter to the parse, parseComposerJson and parseLockfile methods.
We use SemVer for versioning. For the versions available, see the tags on this repository.
If you contribute to this project, you have to ensure that your changes don't mess up the existing functionality.
Therefore this repository comes with a PhpUnit testing configuration, that you can execute by running make test.
See their documentation on more information on how to install the tool.
- Maximilian Schmidt - Owner - MCStreetguy
See also the list of contributors who participated in this project.
Special thanks go to antonkomarev who helped discovering and fixing several deeply nested bugs in the libraries architecture.
This project is licensed under the MIT License - see the LICENSE file for details
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent