I can't speak for Laravel (I don't know it --- See why I dont in Kathy Sierra's Keynote below).
REAL SITUATION: Sucessful projects live a long time. Time on the initial build will be eclipsed by the time spent later. Be kind to your future self, the future team.
TWO SURVIVAL STRATEGIES:
Are things loosely coupled? (not married to one vendor) -- What is the size of tech X's communtiy? is it BIG? Is the language controlled by one dictator for life? Are pieces controlled by one or two vendors? otherwise your technology pillars could go away... Ask Google/Android about Java Licensing. -- Can parts and pieces can be refactored or swapped out with a minimal a ripple affect. example: can a few simple functions be changed to start using GraphQL queries instead of SQL directly?
Cognative Load --- What does it take to understand the code later? will I or my team like looking at / working with the code days, weeks, years from now? Will it be hard to find people later that can work with this stack?
See Kathy Sierra's Keynote "Making Badass Developers" https://www.youtube.com/watch?v=FKTxC9pl-WM
MY Tech Choices My teamI slowly chose to focus on one tech at a time, got comfortable and added as needed. NodeJS, then Express, then React. Later adding OneAuth and LetsEncrypt. We used to hide the database behind a few simple functions from express, I now use GraphQL from inside express to talk to PostGres (SQL). I hope the choices I've made can be corrected later with the offending technology swapped out.
BATTLE SCARS My team started one project in 1989 and it still sees daily use (collecting data, analyzing data). At one time it ran on OS/2 till Microsoft and IBM had a falling out -- WinNT was the result. Pieces written in C still live today (although not Borland C). Custom logic ISA slot cards are gone. Java/Swing compnents has been replaced with JavaScipt/Node/Express/React. Serial cables have been replaced with eithernet cables. Linux towers will soon be replaced with RaspberryPis. Incandecient special shaped fillament bulbs and switches replaced with HDMI touch screens.
Your choices are exciting and it is a wonderful experience to start fresh with so many choices. Future proof your project: keep the tech list short and loosely coupled. Allow yourself to pivot mid-development