Quote:For experts, what do you do with that vendor folder? My app is working fine without all those things composer puts there but I see almost all packages you look for are using composer.
Why does the vendor directory bother you? If your app is working fine with the dependencies that composer installs, why worry about it? I don't understand why anyone would want to waste their time dealing with dependencies manually. Do you actually want to go to each dependency's website and download an individual zip file, unzip it, copy and paste it into your project directory, and then do that all over again when you need to update it for 50 different libraries? Why would anyone want to create this extra work for themselves? Please help me understand.
(11-19-2020, 08:15 AM)captain-sensible Wrote: I didn't used to use composer either, still don't like the duplication of stuff , and as a Linux slackware user like doing everything manually, but composer comes into its own with updates and dependencies .
What i did to vendor so far is this:
Code:
vendor
├── autoload.php
├── codeigniter4
│ └── framework
│ └── system
├── composer
│ ├── ClassLoader.php
│ ├── LICENSE
│ ├── autoload_classmap.php
│ ├── autoload_files.php
│ ├── autoload_namespaces.php
│ ├── autoload_psr4.php
│ ├── autoload_real.php
│ ├── autoload_static.php
│ └── installed.json
├── kint-php
│ └── kint
│ ├── LICENSE
│ ├── README.md
│ ├── build
│ ├── composer.json
│ ├── init.php
│ ├── init_helpers.php
│ ├── resources
│ └── src
├── laminas
│ ├── laminas-escaper
│ │ ├── CHANGELOG.md
│ │ ├── COPYRIGHT.md
│ │ ├── LICENSE.md
│ │ ├── README.md
│ │ ├── composer.json
│ │ └── src
│ └── laminas-zendframework-bridge
│ ├── CHANGELOG.md
│ ├── COPYRIGHT.md
│ ├── LICENSE.md
│ ├── README.md
│ ├── composer.json
│ ├── config
│ └── src
└── psr
└── log
├── LICENSE
├── Psr
├── README.md
└── composer.json
if you look at main :
Code:
ash-5.0$ tree -L 1 CI4
CI4
├── README.md
├── app
├── builds
├── composer.json
├── composer.lock
├── env
├── license.txt
├── phpunit.xml.dist
├── public
├── spark
├── tests
├── vendor
└── writable
the only thing missing that I think is crucial is system ,which is why i did spring cleaning of vendor but left system. After clear out i just ran:
Code:
composer dump
//this refreshes autoload
What is the point of doing this? Seems like you take a chance of introducing breakage and/or regressions by moving things around in vendor, for no apparent benefit. Also how would this scale? You going to do this for each environment your app runs on? Sorry, I don't get it. Seems like a bad idea.