(06-07-2019, 11:46 AM)angrymongol Wrote: (06-07-2019, 10:37 AM)Paradinight Wrote: (06-07-2019, 09:13 AM)angrymongol Wrote: https://stackoverflow.com/search?q=composer
Almost 50k questions. That is way too many questions for a supposedly simple and easy to use dependency manager.
I always liked CI specifically because it worked straight out of the box. There is nothing you need to start working other than that tiny little zip file. That is why I liked kohana too. It had some cool features. Laravel, Symfony, Zend, Cake, etc. Those things require so much unneeded crap just to get the thing running bare. Composer is one of them. So much extra crap you don't need in a production environment either. Docs, examples, other unnecessary files, etc. Let's not kid ourselves. You know over half of the files in node_modules could be deleted and would affect nothing other than disk space.
First composer != npm. Stop compare them. Two different worlds.
You logic is messed up. Most of the big php packages use comoser. Ci4 use composer to add zendframework/zend-escaper as a dependencie.
One of your problems: https://getcomposer.org/doc/01-basic-usa...poser-lock
Read it: https://phptherightway.com/#composer_and_packagist
was kind of continuing on from the post before but sure. read and respond to only what you want. that is totally up to you. "Most of the big php packages" added support for composer, i suppose. They existed before composer and will so after as well.
https://codeigniter4.github.io/userguide...anual.html This must be some next level magic stuff.
I would rather have a single line of code pointing to where an already downloaded, cleaned of junk, and minified piece of code fully under my control than the BS composer tries to do. I mean, look at the links you shared and all the crap you have to do to get it working. How does that make your life easier? So you don't have to know what the hell you are using in your code? I can write an instruction on how to handle packages yourself, by hand in 4 sentences at most. Apparently you need about a magazine worth of instructions to use composer. So tell me, why is it better to use composer? I would say because you don't know how to otherwise.
https://github.com/codeigniter4/CodeIgni...ts.php#L44
https://github.com/codeigniter4/CodeIgni...poser.json
Codeigniter put it for you together... .
If you have the time to download and update all the dependencies by yourself, you should be happy.
Time = money
composer update -> run test -> push to vcs -> create the build -> upload to stageing -> live