1
0
Fork 0

Docs: Place general troubleshooting steps in a more logical order

* `self-update` should be run first, because it may affect the results of `diagnose`. 
* `clear-cache` should be run before `update`, otherwise `update` would need to be run again after clearing the cache.
pull/10086/head
Ian Dunn 2021-08-31 11:44:46 -07:00 committed by GitHub
parent 01d734125c
commit b78570055d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 7 deletions

View File

@ -7,22 +7,22 @@ This is a list of common pitfalls on using Composer, and how to avoid them.
## General ## General
1. Before asking anyone, run [`composer diagnose`](../03-cli.md#diagnose) to check 1. When facing any kind of problems using Composer, be sure to **work with the
for common problems. If it all checks out, proceed to the next steps.
2. When facing any kind of problems using Composer, be sure to **work with the
latest version**. See [self-update](../03-cli.md#self-update) for details. latest version**. See [self-update](../03-cli.md#self-update) for details.
2. Before asking anyone, run [`composer diagnose`](../03-cli.md#diagnose) to check
for common problems. If it all checks out, proceed to the next steps.
3. Make sure you have no problems with your setup by running the installer's 3. Make sure you have no problems with your setup by running the installer's
checks via `curl -sS https://getcomposer.org/installer | php -- --check`. checks via `curl -sS https://getcomposer.org/installer | php -- --check`.
4. Ensure you're **installing vendors straight from your `composer.json`** via 4. Try clearing Composer's cache by running `composer clear-cache`.
5. Ensure you're **installing vendors straight from your `composer.json`** via
`rm -rf vendor && composer update -v` when troubleshooting, excluding any `rm -rf vendor && composer update -v` when troubleshooting, excluding any
possible interferences with existing vendor installations or `composer.lock` possible interferences with existing vendor installations or `composer.lock`
entries. entries.
5. Try clearing Composer's cache by running `composer clear-cache`.
## Package not found ## Package not found
1. Double-check you **don't have typos** in your `composer.json` or repository 1. Double-check you **don't have typos** in your `composer.json` or repository