matchPackageTypes

[LucasDemea]

What would you like Renovate to be able to do?

It would be useful to have an option to filter package types, e.g. composer's "type": "wordpress-plugin".

If you have any ideas on how this should be implemented, please tell us here.

Not familiar enough with renovate codebase.

Is this a feature you are interested in implementing yourself?

No

[rarkins]

Can you point to an example project using these types? Typically this would fit into our depType field but I see we use that for composer already with require and require-dev. One possibility is that we support multiple depTypes, e.g. "depTypes": ["require", "wordpress-plugin"]

[LucasDemea]

You can have a look at roots/bedrock.

It's a custom wordpress stack where plugin are managed as composer dependencies having the wordpress-plugin type.

Typically, you would install a plugin with e.g. composer require wpackagist-plugin/akismet and the composer/installers package would handle the installation in the correct wordpress sub-folder (not vendor) based on the custom wordpress-plugin type.

The composer/installers page shows a list of others packages types examples.

[rarkins]

How/where are types declared? For example it's not in https://github.com/roots/bedrock/blob/f4a3185251566708a4fa14f71bff879d7831aca1/composer.json#L38

I'm trying to understand how Renovate would learn this type, if it's not from composer.json

[LucasDemea]

I think it could be confusing to use the same option to specify "depTypes" and "packageTypes", as this is not represented by the same object in composer.json. The "packageType" is declared in the dependency's composer.json type field, while the "depType" is declared in the project main composer.json.

e.g.
Main project:

{
    "name": "myproject/myproject",
    "type": "project",
    "require": {
        "some/dependency": "^1.0.0"
    }
}

Dependency:

{
    "name": "some/dependency",
    "type": "custom-type"
}

[LucasDemea]

You can use any type you want. There is no list of predefined types. composer/installers makes use of specific types, but you could use any type if you wanted to implement a custom installer, for example.

[LucasDemea]

I don't think Renovate could learn them. It would need to be able to use any arbitrary value.

[rarkins]

So the type can only be learned after downloading the dependency details from packagist?

[LucasDemea]

Idk if it's useful but with composer show you can get the type of an installed package (present in lock file).

e.g. composer show wpackagist-plugin/better-wp-security --format json :

{
    "name": "wpackagist-plugin/better-wp-security",
    "description": null,
    "keywords": [],
    "type": "wordpress-plugin",
    "homepage": "https://wordpress.org/plugins/better-wp-security/",
    "names": [
        "wpackagist-plugin/better-wp-security"
    ],
    "versions": [
        "7.9.1"
    ],
    "source": {
        "type": "svn",
        "url": "https://plugins.svn.wordpress.org/better-wp-security/",
        "reference": "tags/7.9.1"
    },
    "dist": {
        "type": "zip",
        "url": "https://downloads.wordpress.org/plugin/better-wp-security.7.9.1.zip",
        "reference": null
    },
    "path": "/srv/www/cin/current/web/app/plugins/better-wp-security",
    "requires": {
        "composer/installers": "~1.0"
    }
}

[rarkins]

If it's in the lock file then that's easier for us - we can get it during the extract phase