Laravel 5.4 Native authorization. Is it better to make your own from scratch or can you change it?

Question

Laravel

The fact is that in 5.4, for example, a recovery letter comes only with a token, and after clicking on the link from the letter, the user needs to enter his mail again. Although the template has {{$email}} But as I read in the github, this has not been working since version 5.3. And in general, for example, to change the letter, what needs to be done? After all, it is stored in the vendor, so any changes need to be duplicated and classes or methods pulled from there to app ?
For example, I made a recaptcha for all login, registration, password reset methods, I had to duplicate the methods of the native class in my namespace in /app/Http/Controllers/Auth
Since all logic remains in the vendor through trait
How to change native Auth correctly ?
Or it’s easier and better to write from scratch, since native is just an example that hasn’t been fully completed and a lot of it doesn’t work out of the box.
This problem is also not solvable https://github.com/laravel/framework/issues/15733 , the more I look, the more I understand that native authorization is just an example that needs to be finished and finished, and moved everything to space / app from vendor...

Answer 1

php artisan make:auth

Answer 2

As for the form - Tyk - I don’t know if it is or not.
Recaptcha: why? I once took Google captcha (there is a package on the git), and all that needed to be done was to add it to the validation when posting (well, display it in the form : D
) adequate.
And if the whole problem is password recovery - write your service, what's the problem? :)