What is Laravel Jetstream?

In this video I explore Laravel Jetstream. I go through the installation and setup process for both Jetstream Livewire and Jetstream Inertia. I also go through some of the pros and cons of this Laravel package.

[@beautifulmenory]

Thank you sir. this video is one of the best Jetstream tutorial ever I've seen.

[@AndreasBeder]

Just started a project with Jetstream and inertia and absolutely love it.

[@3mro_coding]

Nooo please :( We need Api for mobile apps. I use laravel because of the ability to build front and mobile backend. I won't be able to use inersia at all. Does the livewire do the same.

[@waiylkarim]

I love the way you explain and go through each aspect in such smoothness. Keep it up man! And as for the API issue, in my opinion you can create a repository inside your App folder, and use it to as your logic gateway. For example, you'd have a UsersRepository, InvoicesRepository and InventoryRepository. Every repository will have the its own logic. You could use this repository either as a trait or typehint it on your Controllers constructors to avoid code duplication. Intertia controllers and your own API controllers will use these repositories without having to recreate the logic for each controller. This is just an initial random solution I've got while watching your video. I didn't try it to see how the workflow and effectiveness will be. But if you could try it yourself and make a video about it or about any other similar and interesting solutions I've read on the comments, it would be nice for newbies to try it. Again, amazing channel, this is the first video I watch in your channel but it was more than enough to smash the like and subscribe button. Keep it up and I encourage you to add the Join button (YPP) to your channel. You deserve encouragement!

[@TheRegehr]

Hi, great video, thank you! About the API problem, what about the solution to check wether or not the request wants a json response like this: if (request()->wantsJson()) { return $users; } return Inertia::render('Users', [ 'users' => $users ]);

[@samuelpradhan1899]

Thanks for your valuable information

[@surajoliver1]

I was not feeling comfortable using Inertia. You said it well...

[@hirenjoshi2198]

Nice explanation about the new stuffs introduced by Laravel along with its drawbacks. Will it be OK to use Laravel Fortify + Vue for the solution about API base application which Intertia doesn't provide. Please share your knowledge on how to handle it and make that happen without Jetstream but with Fortify.

[@scrypster]

You can use Laravel fortify by itself without jetstream. You just need to create all the frontend views yourself. The architecture really depends on what you need to accomplish. There really is no one size fits all.

[@user-tt6nc6mo7k]

So is Jetstream secure for me to just use as is on client projects? Like lets say I was creating an ecommerce website and wanted users to be able to login and see their orders etc.

[@scrypster]

Yes. However, a poorly designed application can introduce security holes. So you still want to follow best practices when it comes to security. Jetstream is a good foundation, but you still want to enforce a high security standard for your app. HTTPS, harder password formats, etc.

[@nopass4980]

i really enjoy your channel the way you explain stuff is really great ! plus the documentation based tutoring is awesome it motivates me to read more ! i have a question : does a mobile app or and independent front-end sends the same request type to the back-end as inertia driven app ? can't we check the type the request like laravel does to differ between json content response and http full pages response ?

[@scrypster]

Thank you! If you look at Chrome Developer Tools under the network tab, when you send a request with inertia, you still specify a post or put or whatever you need. Then if you look at the data sent at the bottom of the network tab, it goes to the backend the same way as it would without inertia. So the backend doesn’t know it’s inertia sending the request. But when you specify in your backend to send an inertia style response, it returns inertia formatted data. The reason they use inertia on the frontend is to wrap the request, so when it’s received, inertia on the frontend can parse out the inertia syntax received from the backend. I hope that makes sense.

[@nopass4980]

@@scrypster thank you for the explanation . so laravel treats inertia requests as a non json request therefore cannot tell the difference between inertia request or normal request . I never used inertia before , but i love the idea of sending an inertia formatted object as response ! Its super interesting

[@MostInterestingManInTheWrld]

About the JSON API thing, why don't you (theoretically) add something like this before returning Inertia::render ... // Illuminate\Http\Concerns\InteractsWithContentTypes::expectsJson if ($request->expectsJson()) { // return json data } return Inertia::render(...

[@mostafa5863]

Please increate your tune in videos

[@DevosystemSafi]

A NICE CHAIN THE PROBLEM AT THE CODE DISPLAY LEVEL. IT'S VERY SMALL

[@MorganLee1997]

Does Laravel Jetstream works well with VueJS 3.0?

[@AndreasBeder]

It does very well.

[@adrianfiddy2161]

Great content from aspects of clear audio, speed and depth of detail. Thumbs up. www.think.do 🧠 looking forward to more.👍

[@bylde4791]

So basically if you are developing an app which will need API's do not use inertia use livewire

[@Jake-bh1hm]

Thanks for making this. But I have a newb question, so with jet stream livewire, the issue with it not being api forward is not there correct? Because it uses blade templates and traditional routes?

[@kplgr]

Longtime laravel developer here, who hasn't yet bothered trying out jetstream but I am thinking about it for a project. You just helped me dodge a (future) bullet by sharing your considerations regarding the absence of pure API routes when using Inertia, I would have probably noticed that too late. I don't really know livewire either, but I am wondering if selecting that path instead of inertia & vue would be any easier down the road. Anyway, you have earned yourself a subscriber for the awesome content you upload. Thank you !

[@aymenopa3563]

after i forked jetstream package i converted vue to React i handled inertia configuration ,fixed jsx interpretation and converted all Vue files to react i only touched the front end part so it's doesn't effect on jetstream logic files please contact me if you want source code

[@johnsito]

Hi your content really help us the beginners thank you so much. please can you tell me which stack you will choose for a web application and API support.

[@johnandrew721]

So what you are really saying at the last segment of the video is that for a Laravel API, it won't matter if I use Inertia or Livewire. Is that statement correct?

[@AntonioCabralNumberOne]

Hi! I'm recent to Laravel and even newer to Vue. In the end you've told that using Jetstream Inertia would kind of stifle a possible future growth because it's still a monolith, instead of using more heavily API to be used by mobile, etc. Would you think sacrificing speed to lauch a product (jetstream-inertia) by making a strong API but still using Vue with vanilla laravel (with Fortify and/or Sanctum) would be the best alternative? If not what would you guys suggest? Great video, anyways! Kudos!

[@robywankenoby1968]

Have you noticed how becomes messy to find the routes you expose when you type php artisan route:list with jetstream inertia?

[@rubinbajracharya9319]

Great video. But how do we expose all the feature for api authentication and authorization so that I can make something for mobile and other platform as well?

[@thatsenam9183]

Keep it up. Already loving

[@apriljoyaltiche3298]

I hope this channel gets the views it deserve. keep it up. you are my new fave now. hehe Thank you!

[@josuebarros-desenvolvedorw2490]

Your channel is a GOLD MINE! Congratulations with this excellent channel bro! Please, create a news portal with TALL stack (TailwindCSS, AlpineJS, Livewire, Laravel) Salutes from Brazil!

[@scrypster]

Thanks Josue! What kind of things would you like to see in a News Portal? I have a few other videos lined, but if time permits, I’ll see what I can do.

[@josuebarros-desenvolvedorw2490]

@@scrypster you're welcome! I think if you create a project like that edition.cnn.com/ you'll be unique! I never found anyone on youtube that created a project like this ;)

[@josuebarros-desenvolvedorw2490]

@@scrypster Inertia or Livewire, AlpineJS, TailwindCSS... there is a lot of options, Laravel's ecossystem is sooo rich BTW, NuxtJS helps a lot bringing Vuex, Vue-Router and Vue-meta from start

[@josuebarros-desenvolvedorw2490]

If your schedule permits of course, you can even start planning to create this serie later 2021 like July... But is going to be a badass project hehe: things like including images, journalist names, categories. Is almost like a simple crud, but with a lot of details and relations inside a SQL database (MySQL, PostgreSQL, Oracle...)

[@narekvardapetyan8911]

Thanks. Good tutorial. Can You add github link?

[@imanparvizi9973]

Keep going nice

[@mannabua]

This is awesome! Thank you for this. About the API part for future mobile app, I believe we can achieve it by using Traits in the core functions of our applications in that way we will never rewrite the codes again for the core process and can easily manage it for different controllers for the API not using Inertia. Just my taught, will work on this for my next web application.

[@alifirhas3550]

For people like me who have a headache watching this tutorial. Be patient, at 28:38 minutes your headaches will disappear.

[@arturoatencio1433]

Hi, great video man! Just thinking about what you said at the end of it, what would you use then regarding that inertia problem? would you use livewire insted or some sort of customization for the returning objects? And also, if you go with inertia, is no other way to return object to the view that is actually able to be rendered other than that inertia object? Thanks.

[@hafizaqibakhtar9692]

Earned a Subscribe Bro, Keep it up!

[@risnanto]

Man, you’re really good at explaining all the content

[@tafappfabricadeaplicativos4470]

Thanks!!!

[@lesssass4478]

Expecting more laravel vue content.

[@islandblaze007]

Great stuff man! Excellent delivery!

[@virgiliustancu9293]

I have this error when I run npm run dev: code ELIFECYCLE npm ERR! errno 1 npm ERR! @ development: `mix` npm ERR! Exit status 1 Do you have a solution for that? Thanks!

[@lesssass4478]

try this. rm -rf node_modules rm package-lock.json yarn.lock npm cache clear --force npm install

[@virgiliustancu9293]

@@lesssass4478 I tried but didn't worked. The problem was with the "mix" word in the package.json . I changed the scripts to avoid "mix" with: "dev": "npm run development", "development": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --config=node_modules/laravel-mix/setup/webpack.config.js", "watch": "npm run development -- --watch", "watch-poll": "npm run watch -- --watch-poll", "hot": "cross-env NODE_ENV=development node_modules/webpack-dev-server/bin/webpack-dev-server.js --inline --hot --disable-host-check --config=node_modules/laravel-mix/setup/webpack.config.js", "prod": "npm run production", "production": "cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --no-progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js" This was my solution. I have more to learn about those configuration files.

[@ivangeofrey4785]

The problem is old nodejs version of your system and project so you must update to latest version

[@chrisbailey2098]

I will never understand how PHP is still relevant seeing as it relies on JavaScript, node and npm so much now. I know many many people are trained and have careers based upon it but it's about time PHP got sent to live on the farm.