How does working with composer relate to Laravel (need some practical advice)?

Question

Laravel

Hello!
I again had a question about how to change the folder for the views created by the make:auth command.
For the login.blade.php view, it turned out to be simple - it is registered in the controller, but the rest, including the registration view, are registered in no clear place at all, and I don’t I understand what to do with it.
I started to google - they write that it is somehow connected with the composer and you need to edit some paths and then do it. composer dumpautoload
But I don’t understand anything at all, but I don’t like to edit what I don’t understand.
Is there any easier way to change the path to authentication views from auth to subdir/auth
Well, in general, what does this composer have to do with it? Why is it needed at all, if you just need to fix the path? Why complicate simple things? (to be honest, this is already starting to annoy a little - a bunch of extra entities out of the blue constantly crawl out).

Answer 1

RegisterController->showRegistrationForm() { return view('my_reg_form'); }
LoginController->showLoginForm() { return view('my_login_form'); }
ResetPasswordController->showResetForm() { return view('my_reset_form'); }
https://laravel.com/api/5.7/search.html?search=show