Ryan Chandler

I'm going to be honest with you all for a second.

I'll start off by going over what the Pipeline class actually does.

Since Alpine lives directly in the markup, it can be difficult to abstract components in the correct way.

Anyone who is familiar with Livewire has probably used computed properties at some point.

DRY code is important and it can be difficult to be completely DRY with your code, especially when you're using a front-end framework such as Alpine.

I think jQuery's greatest feature is all of the animation / transition utilities.

I'd estimate that 99% of Laravel applications register their routes using the Illuminate\Support\Facades\Route class.

Most applications use jobs as a way of pushing heavy logic off of the main thread and doing work asynchronously, in the background.

In most applications validation logic is placed in standardised places.

Generally speaking, the easiest way to do this is comparing the name of the current route and the one you'd like to test against.

Have you ever needed access to the current user's name or email address in your applications JavaScript?

Livewire's polling API is great for periodically refreshing your component or invoking an action, but one of the more quietly documented features is the ability to manually refresh a component using a "magic" action.

Lots of applications involve date and time manipulation.

When a customer at Surewise wants to take out a new insurance policy, they can only take one out with a start date within the next thirty days.

The "Repository pattern" is essentially another level of abstraction on top of your database abstraction layer.

Since Alpine doesn't have a virtual DOM and doesn't compile your templates, it evaluates a component's directives procedurally, in the order that they are defined.

If you've used Alpine before, you might have seen a brief flick when you load your site up.

I've been using Alpine for the last couple of months in most of my projects and have experimented with different organisation patterns that improve the maintainability of my components.

Although there's many ways to do this in Laravel, the simplest way is with a piece of web middleware.

The other day, I wrote an article on how to achieve a similar effect to computed properties in Alpine.js.

At its core, Alpine depends on an x-data attribute.

I've been trying to use Alpine.js more and more throughout my projects, both personal and professional.

For anyone who has used PHP before, you're probably familiar with the array_unique() function.

For example, after a model gets created I don't want anyone to be able to update that record again.

If you're a part of the Laravel community, you've probably already heard of Alpine.