The purpose of extracting the make: auth package is that the developer can choose to develop on the front side either using react,vue, boostrapt and thus separate the views of this package, allowing him to decide and that it is no longer the framework who does it for the!!
regarding why, there must be some architectural reason. I don't know in particular.
and yes I also believe that make:auth was more appropriate but this a small part of something big.
and yes we have to run "npm install && npm run dev" after?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
My question is: why?
Make:auth was so intuitive...
Also: should you run "npm install && npm run dev" after?
The purpose of extracting the make: auth package is that the developer can choose to develop on the front side either using
react
,vue
,boostrapt
and thus separate the views of this package, allowing him to decide and that it is no longer the framework who does it for the!!regarding why, there must be some architectural reason. I don't know in particular.
and yes I also believe that make:auth was more appropriate but this a small part of something big.
and yes we have to run "npm install && npm run dev" after?