[wp-trac] [WordPress Trac] #36335: Next generation: core autoloader proposal

[WordPress Trac]

#36335: Next generation: core autoloader proposal
-----------------------------+------------------------------
 Reporter:  dnaber-de        |       Owner:  (none)
     Type:  feature request  |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  General          |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  has-patch        |     Focuses:
-----------------------------+------------------------------

Comment (by jqz):

 Replying to [comment:258 omaeyusuke]:
 > - Minimize the number of files generated by third-party projects
 (Composer)

 I don't understand this concern.  AFAIK, Composer doesn't generate any
 superfluous files.

 Some packages include their development dependencies in the wrong section
 of `composer.json` so they end up getting installed unnecessarily, but
 that's an issue with those specific packages, not Composer itself.

 > However, in June 2022, the class map generation implementation of
 Composer was released as a separate package.

 Don't we also need the package installer component of Composer?  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.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36335#comment:259>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform