Stacks are a means to an end. And as good as Angular and React stacks are, there is something to be said for the value proposition of good ole php stacks (laravel, vue etc).
Getting good at a stack will start to specialize you. Thats fine, but remember that as you start changing jobs and grow, you might have to know other things so, more important that a particular stack, is how stacks work in general.
Do you know linux? If not, then you should start. If you are writing web software (stacks, apps, etc) they are most likely going to run on linux somewhere in the aether or someone eles's computer (read: cloud). Homestead (laravel/php ) is fine, but getting used to ACTUAL linux, apache or nginx experience is paramount. You're going to have to mess with it sometime in the future, might as well get it now.
My resume is about 18 years of "private, proprietary, in-house" software. I have NOTHING out in the github world for people to see (and I still get calls/emails a few times a week asking me to consider working here or there). Its DEFINITELY a route you can go, but only if you want to, or get something out of it. If you're trying to write books about this stuff, then yeah, otherwise, I haven't needed it, so you might not either.
"Amateur" is an often misunderstood, misused word. The word is french I think, but it means someone who does something for the love of it. By that measure, I am am amateur. ;) Anywho, TELLS are simple. When I ask a candidate about a particular line-item in their resume, and they start to shift around, I think they are uncomfortable.
One of my personal favorite things to do, is to ask the candidate about the ACRONYM-SOUP in their sills list. I don't put ANYTHING on my resume I can't speak about, so if I see "AJAX" on yours, you had better damn-well know what it stands for, or, I can now assume you are just padding that document to get in the door. To me, its a bad idea, so I'll be digging around for other bad ideas in there.