If the installation fails and the NSX VIBs are not copied to the boot disk, an ESXi host works as expected until the next reboot.
Upon that reboot, NSX host preparation fails as no VIBs are available in the running image of the system.
The best way to ensure this is to list them in an option file. That section also describes option file format and syntax.
But you need a different version of said package B (say 0.11).
You can fix this by aliasing version 0.11 to 0.1: composer.json: This issue can also happen on c Panel instances, when the shell fork bomb protection is activated.
Because of that in some cases it will not be a practical workaround, and you should always try to switch to tagged releases as soon as you can. It is therefore strongly recommended that you do not use it.
Let's say your project depends on package A, which in turn depends on a specific version of package B (say 0.1).