Context Navigation

Changes between Version 2 and Version 3 of Ticket #36335, comment 261

v2	v3
1	1	Replying to [comment:259 jqz]:
2	2	> I don't understand this concern. AFAIK, Composer doesn't generate any superfluous files.
3		No, there are files that are required considering the resolution of dependencies on packages created by third parties, but unnecessary considering only the autoloader into the core (e.g., autoload_psr4.php, autoload_real.php, autoload_namespace.php) .
	3	No, there are files that are required considering the resolution of dependencies on packages created by third parties, but unnecessary considering only the autoloader into the core (e.g., autoload_psr4.php, autoload_real.php, and autoload_namespace.php) .
4	4	If you do not do dependency resolution for third-party created packages, most of them could simply be overhead if we use Composer as a whole.
5	5	> Isn't the point of this to reduce the number of files, as well as eliminating version conflicts when two plugins ship with incompatible versions of a third-party package, by sharing common packages between plugins/themes, and having WordPress download and install the dependencies to a common folder (e.g. wp-content/packages) rather than the plugins/themes having to ship with separate copies of these common packages.