D7net Mini Sh3LL v1
Current File : //libx32/../share/snapd/../locale/ia/../../doc/info/../libroken18-heimdal/../usbmuxd/../liberror-perl/../grub2-common/../libjpeg8/../php7.4-mysql/../gnupg/../python3-apt/../netplan.io/../wget/../libcurl3-gnutls/../libthai-data/../python3-six/../screen/../maria/../libxaw7/../libunwind8/../python3/../libxslt1.1/../libtool/../libncursesw6/../libgvpr2/../libatasmart4/../debianutils/../libfdisk1/../gcc-9/../dbus/../info/../libpam-cap/../libutempter0/../libcrypt1/../python3-attr/../cron/../lsof/../fdisk/../libcdt5/../libsemanage1/../libasan5/../libcurl4/../liblmdb0/../psmisc/../libxdmcp6/../libpython3.8/../modemmanager/../telnet/../libcom-err2/../modemmanager/../libudev1/../linux-modules-5.4.0-144-generic/../mariadb-server-10.3/../libdconf1/../squashfs-tools/../composer/faqs/how-do-i-install-a-package-to-a-custom-path-for-my-framework.md |
# How do I install a package to a custom path for my framework?
Each framework may have one or many different required package installation
paths. Composer can be configured to install packages to a folder other than
the default `vendor` folder by using
[composer/installers](https://github.com/composer/installers).
If you are a **package author** and want your package installed to a custom
directory, simply require `composer/installers` and set the appropriate `type`.
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:
```json
{
"name": "you/themename",
"type": "wordpress-theme",
"require": {
"composer/installers": "~1.0"
}
}
```
Now when your theme is installed with Composer it will be placed into
`wp-content/themes/themename/` folder. Check the
[current supported types](https://github.com/composer/installers#current-supported-package-types)
for your package.
As a **package consumer** you can set or override the install path for a package
that requires composer/installers by configuring the `installer-paths` extra. A
useful example would be for a Drupal multisite setup where the package should be
installed into your sites subdirectory. Here we are overriding the install path
for a module that uses composer/installers:
```json
{
"extra": {
"installer-paths": {
"sites/example.com/modules/{$name}": ["vendor/package"]
}
}
}
```
Now the package would be installed to your folder location, rather than the default
composer/installers determined location.
> **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
> that it handles.
AnonSec - 2021 | Recode By D7net