We're mostly finished. I only want to make a couple tweaks and then we'll call it a series. So if we go to our laracast preset file, one thing I noted in the last episode is I'd still like a sass directory with a starting app.sass file. So I can say update styles, and we'll scroll down here. Now again, if there's a stub you want to use, then we can create that. In my case, just an empty file would be fine for me. So why don't we say file, put to the resource path, assets, sass, and then app.sass. Now if you want to hard code some beginning styling, you can, but I don't need to. All right, and I'll leave it to you to add anything else you want.

Now if you want to hard code some beginning styling, you can, but I don't need to. All right, and I'll leave it to you to add anything else you want. So one more time, we'll give this a run. And now if I switch back, yeah, there's our app.sass file where you can get started. Okay, so I'm going to grab that in my web directory, switch back to our Laravel preset and paste it in. Now if we do a git status, there we go, we'll say update styles and push it up. Now as part of this, of course, you can create a new version. In my case, DevMaster is fine because presumably I'm the only one who would ever use it. But if it is something you want to release to others, you might want to tag a full release.

In my case, DevMaster is fine because presumably I'm the only one who would ever use it. But if it is something you want to release to others, you might want to tag a full release. Anyhow, if we give this a refresh, you can see the latest version has been updated. So our only remaining step is to switch back. I'll create a new project one last time. I'll cd in there. We'll then require our Laravel preset that will automatically register itself and we'll be all set to go. All right, so in Sublime, one final time, here's our mix file, here's our JavaScript, there's a components directory, here's our sass and all of that, and then here's our

All right, so in Sublime, one final time, here's our mix file, here's our JavaScript, there's a components directory, here's our sass and all of that, and then here's our package.json that includes a bunch of stuff. We're now going to use our custom preset, php artisan preset laracasts. All right, and we did forget the output. I'll do that on my own behind the scenes and I'll show you how to do that at the end of the video. But anyways, now we've decreased that, we've emptied this out, we've modified this. If you want to get rid of that components directory, you can add that as a step as well. Finally, webpack.mix has been cleaned up.

If you want to get rid of that components directory, you can add that as a step as well. Finally, webpack.mix has been cleaned up. Okay, so yeah, you know what? We're basically finished here. Like I said, the only remaining thing you might want to do is here, say php artisan info, all finished. Please compile your assets and you are all set to go. Something like that. And if you want to see that, we'll just do it together. LaracastServiceProvider, paste that in.

And if you want to see that, we'll just do it together. LaracastServiceProvider, paste that in. And yeah, if we do it one more time, there you go. You get your output. All right, and that's it. So this is everything you need to know to begin creating your own custom Laravel presets.