From a47f44bc61a17b70ef7d5d1f03bfd0336df87044 Mon Sep 17 00:00:00 2001 From: Tianni Date: Tue, 7 Apr 2020 15:10:00 -0400 Subject: [PATCH] docs updated install package custom path --- ...o-i-install-a-package-to-a-custom-path-for-my-framework.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/faqs/how-do-i-install-a-package-to-a-custom-path-for-my-framework.md b/doc/faqs/how-do-i-install-a-package-to-a-custom-path-for-my-framework.md index 20a2e83ae..a81db4799 100644 --- a/doc/faqs/how-do-i-install-a-package-to-a-custom-path-for-my-framework.md +++ b/doc/faqs/how-do-i-install-a-package-to-a-custom-path-for-my-framework.md @@ -7,6 +7,7 @@ the default `vendor` folder by using If you are a **package author** and want your package installed to a custom directory, simply require `composer/installers` and set the appropriate `type`. +Specifying the package type, will override the default installer path. This is common if your package is intended for a specific framework such as CakePHP, Drupal or WordPress. Here is an example composer.json file for a WordPress theme: @@ -43,7 +44,8 @@ for a module that uses composer/installers: ``` Now the package would be installed to your folder location, rather than the default -composer/installers determined location. +composer/installers determined location. In addition, `installer-paths` is order-dependent, which means moving a package by name + should come before the installer path of a `type` that matches the same package. > **Note:** You cannot use this to change the path of any package. This is only > applicable to packages that require `composer/installers` and use a custom type