For example, if I have to remove a package (obsolete package), how can I verify that it does not have dependents?
SupaPlex:
[...]
For example, if I have to remove a package (obsolete package), how can I
verify that it does not have dependents?
You can try: composer show --tree
Il 22/06/22 14:33, Arno Welzel ha scritto:
SupaPlex:
[...]
For example, if I have to remove a package (obsolete package), how can I >>> verify that it does not have dependents?
You can try: composer show --tree
Composer could not find a composer.json file
To initialize a project, please create a composer.json file as described
in the https://getcomposer.org/ "Getting Started" section
SupaPlex:
Il 22/06/22 16:07, Arno Welzel ha scritto:
Why do you try to use Composer outside a folder with composer.json?
why shouldn't I do it?
Because composer.json is the file where your dependencies are defined.
Also see: <https://getcomposer.org/doc/01-basic-usage.md>
Why do you try to use Composer outside a folder with composer.json?
Il 22/06/22 16:07, Arno Welzel ha scritto:
Why do you try to use Composer outside a folder with composer.json?
why shouldn't I do it?
Il 22/06/22 16:37, Arno Welzel ha scritto:
SupaPlex:
Il 22/06/22 16:07, Arno Welzel ha scritto:
Why do you try to use Composer outside a folder with composer.json?
why shouldn't I do it?
Because composer.json is the file where your dependencies are defined.
Also see: <https://getcomposer.org/doc/01-basic-usage.md>
What dependencies should i define?
The info I want is for packages global level, not for single project (*/composer.json).
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 379 |
Nodes: | 16 (2 / 14) |
Uptime: | 68:08:18 |
Calls: | 8,084 |
Calls today: | 2 |
Files: | 13,068 |
Messages: | 5,849,529 |