Add composer.json for easier inclusion in projects

Makes it easier to handle extension updates in composer-managed projects.

(I'm messing around with composer so that it's easier for our shop to update our various builds, track versions, etc)

@sluc23 thoughts?

looks good to me
There's another property that is useful in composer.json, which is type, but there's not yet a clear general convention about which value to use here.. we use internally "type": "civicrm-extension" (as here ).. it helps to place extensions automatically in an specific folder, for example if defined in the main composer.json as

{
    . . .
    "repositories": [
        . . .
    ],
    "require": {
        . . .
    },
    "extra": {
        . . .
        "installer-paths": {
            . . .
            "web/modules/contrib/{$name}": [
                "type:drupal-module"
            ],
            "web/themes/contrib/{$name}": [
                "type:drupal-theme"
            ],
            "vendor/civicrm/{$name}": [
                "type:civicrm-extension"
            ]
        },
    },
    . . .
}

but this is a discussion we can have in a different issue

@sluc23 Good point - I added the type property.

added 1 commit

• d641fe71 - Add composer.json for easier inclusion in projects

Compare with previous version

mentioned in commit 5dada8bc

merged