May 25, 2021 Composer
When you use custom libraries, you may run into problems because Composer does not recursively load all the
composer.json
Before you elaborate on why this is the case, you need to understand: use a custom VCS and package repository to try something, or use a branch of your fork until your pull request is merged, and so on. You shouldn't use them to track your private resource packs, and you should look at setting up Satis to handle private resource packs for your company or even yourself.
Here are three ways to make the dependency parser use your custom repository:
Read the repository of the root package, get all the packages from the defined repository, and resolve the dependency requirements. This is the current state, and it works well, except for the "unrecursive load repository" limit.
Read the repository of the root package, initialize the resource package from the defined repos, recursive initialization, based on the repos defined in all dependent packages, and the repos defined in the other packages on which the dependent package depends, and so on, and then parse the dependent requirements. T his may work, but it can seriously affect the speed of initialization, as it takes a few seconds for each VCS repos to be read. I t may eventually fail because different versions of a package may come from the same package in a package repository, but come to a different dist/source. There are too many things that can go wrong.