The Ultimate Vue.js & Laravel CRUD Tutorial
CRUD (Create, Read, Update and Delete) are the basic operations of data storage, and one of the first things you learn as a Laravel developer.
But what happens when you add a Vue.js single-page app as the frontend to this the stack? Suddenly you have to deal with asynchronous CRUD, since operations now occur without a page refresh. This will require special attention to ensuring the state of the data is consistent in both the front end backends.
In this tutorial, I’ll show you how to set up a full-stack Vue & Laravel app and demo each of the CRUD operations. AJAX is the key to this architecture, so we’ll use Axios as the HTTP client. I’ll also show you some strategies for dealing with the UX pitfalls of this architecture.
You can check out the finished product in this GitHub repo.
Note: this article was originally posted here on the Vue.js Developers blog on 2018/02/05
The demo full-stack app allows a user to create new “Cruds”, which I decided, after an incredible amount of creative thinking, are alien creatures with strange names and the ability to change from red to green and back.
The Cruds are shown on the main page, and the user has the power to create new Cruds, to delete them, or to update their color.
CRUD in the Laravel backend
We’ll begin the tutorial with the Laravel backend where the CRUD operations are fulfilled. I’ll keep this part brief as Laravel CRUD is a topic covered extensively elsewhere.
In summary, we will:
- Set up a database
- Set up RESTful API routes by using a Resource Controller
- Define methods in the controller to perform the CRUD operations
Firstly, the migration. Our Cruds have two properties: a name, and color which we store as text.
Now we set up RESTful API routes. The
resource method of the
Route facade will create all the actions we need automatically. However, we don't need
store so we'll exclude those.
With this in place, here are the various endpoints we’ll now have available in our API:
We now need to implement those actions in the controller:
Let’s do a brief overview of each method:
create. We randomize the name and color of a new Crud using the
Faker package included with Laravel. We send the new Crud data back as JSON.
index. We return the full set of Cruds with the
index method. In a more serious app we'd use pagination, but let's keep it simple for now.
update. This action allows a client to change the color of a Crud.
destroy. This is how we delete our Cruds.
Now for our Vue single-page app. We’ll begin by creating a single-file component to represent our Cruds called
This component is just for display and doesn’t have much logic. Here are the noteworthy aspects:
- The image shown depends on the color of the Crud (either red.png or green.png)
- Has a delete button which triggers a method
delon click, which emits an event
deletewith the ID of the Crud
- Has an HTML select (for choosing the color) which triggers a method
updateon change, which emits an event
updatewith the ID of the Crud and the new color selected
The other component in this project is App.js. This is where all the interesting logic occurs so we’re going to go through this one step-by-step.
Let’s begin with the template. This has the following jobs:
- Display our Cruds with the
crud-componentcomponent discussed above
- Loop through an array of Crud objects (in the array
cruds), with each mapping to an instance of
crud-component. We pass all the properties of a Crud through to the component as props, and set up listeners for the
deleteevents coming from the component
- We also have an Add button that will create new Cruds by triggering a method
script from App.js. Let's talk this out too:
- We start with a function
Crudthat creates new objects used to represent our Cruds. Each has an ID, color, and name
- We import the adjacent
- The component definition contains the array
crudsas a data property. I've also stubbed methods for each CRUD operation which will be populated in the next section
Triggering CRUD from the frontend with AJAX
All the CRUD operations in a full-stack app will be executed in the backend since that’s where the database is. However, the triggering of CRUD operations will often happen in the frontend.
As such, an HTTP client (something that can communicate between our front and backends across the internet) will be of importance here. Axios is a great HTTP client that comes pre-installed with the default Laravel frontend.
Let’s look at our resource table again, as each AJAX call will need to target a relevant API endpoint:
Let’s begin with the
read method. This method is responsible for retrieving our Cruds from the backend and will target the
index action of our Laravel controller, thus using the GET endpoint /api/cruds.
We can set up a GET call with
window.axios.get, as the Axios library has been aliased as a property of the
window object in the default Laravel frontend setup.
Axios methods like
post etc return a promise. We chain a
then method with a callback to access the response. The object resolved can be destructured to allow convenient access to the
data property in the callback, which is the body of the AJAX response.
Crud factory function, then push them to the
cruds array data property i.e.
Note: We need to trigger the
readmethod programmatically when the app loads. We do this from the
createdhook, which works, but is not very efficient. It'd be far better to get rid of the
readmethod altogether and just include the initial state of the app inlined into the document head when the first loads. I discuss this design pattern in depth in the article Avoid This Common Anti-Pattern In Full-Stack Vue/Laravel Apps if you want to implement it.
With that done, we can now see the Cruds displayed in our app when we load it:
Update (and syncing state)
update action requires us to send form data, i.e.
color, so the controller knows what to update. The ID of the Crud is given in the endpoint.
This is a good time to discuss an issue I mentioned at the beginning of the article: with full-stack apps, you must ensure the state of the data is consistent in both the front and backends.
In the case of the
update method, we could update the Crud object in the frontend app instantly before the AJAX call is made, since we already know the new state.
However, we don’t perform this update until the AJAX call completes. Why? The reason is that the action might fail for some reason: the internet connection might drop, the updated value may be rejected by the database, or some other reason.
If we wait until the server responds before updating the frontend state, we can be sure the action was successful and the front and backend data is synchronized.
You might argue its bad UX to wait for the AJAX to resolve before showing the changed data when you don’t have to, but I think it’s much worse UX to mislead the user into thinking a change is done, when in fact, we aren’t sure if it is done or not.
Create and Delete
Now that you understand the key points of the architecture, you will be able to understand these last two operations without my commentary:
Loading indicator and disabling interaction
As you know, our CRUD operations are asynchronous, and so there’s a small delay while we wait for the AJAX call to reach the server, for the server to respond, and to receive the response.
To improve UX it’d be good to have some kind of visual loading indicator, and to disable any interactivity while we wait for the current action to resolve. This lets the user know what’s going on, plus, it gives them certainty of the state of the data.
There are some good plugins for Vue.js loading state, but I’m just going to make something quick and dirty here: while AJAX is underway I’ll overlay a full screen, semi-transparent
div over the top of the app. This will kill both the mentioned birds with a single stone.
To do this, we’ll toggle the value of a boolean
mute from false to true whenever AJAX is underway, and use this value to show/hide the
Here’s how we implement the toggling of
mute in the
update method. When the method is called,
mute is set to true. When the promise resolves, AJAX is done so it's safe for the user to interact with the app again, so we set
mute back to false.
You’ll need to implement the same thing in each of the CRUD methods, but I won’t show that here for brevity.
To make our loading indicator markup and CSS, we add the element
<div id="mute"></div> directly above our mount element
As you can see from the inline style, when the class
on is added to
<div id="mute">, it will completely cover the app, adding a greyish tinge and preventing any click events from reaching the buttons and selects:
The last piece of the puzzle is to toggle the
on class by utilizing a
watch on the value of
mute, which calls this method each time
With that done, you now have a working full-stack Vue/Laravel CRUD app with a loading indicator. Here it is again in its full glory:
Don’t forget to grab the code in this GitHub repo and leave me a comment if you have any thoughts or questions!
Get the latest Vue.js articles, tutorials and cool projects in your inbox with the Vue.js Developers Newsletter