A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/zendframework/zend-component-installer/ below:

zendframework/zend-component-installer: Composer post-package-(un)install scripts for modules and components.

Component Installer for Zend Framework 3 and Expressive Applications

Repository abandoned 2019-12-31

This repository has moved to laminas/laminas-component-installer.

This repository contains the Composer plugin class Zend\ComponentInstaller\ComponentInstaller, which provides Composer event hooks for the events:

Via Composer global install

To install the utility for use with all projects you use:

$ composer global require zendframework/zend-component-installer

To install the utility for use with a specific project already managed by composer:

$ composer require zendframework/zend-component-installer
Writing packages that utilize the installer

Packages can opt-in to the workflow from zend-component-installer by defining one or more of the following keys under the extra.zf configuration in their composer.json file:

"extra": {
  "zf": {
    "component": "Component\\Namespace",
    "config-provider": "Classname\\For\\ConfigProvider",
    "module": "Module\\Namespace"
  }
}
Whitelisting packages to install automatically

At the project level, you can mark packages that expose configuration providers and modules that you want to automatically inject via the component-whitelist key:

"extra": {
  "zf": {
    "component-whitelist": [
      "zendframework/zend-expressive",
      "zendframework/zend-expressive-helpers"
    ]
  }
}

This configuration must be made at the root package level (the package consuming configuration providing packages).


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4