Cover image for Using async await with jQuery’s $.ajax

Using async await with jQuery’s $.ajax

ptasker profile image Peter Tasker Originally published at petetasker.com on ・4 min read

Photo by Denys Nevozhai on Unsplash

If you’re like me, you’re probably stuck using jQuery more often than not. It’s everywhere, and to be honest it’s a solid, mature library. It’s also often already loaded on the page, especially if you’re working with WordPress.

Outside of DOM manipulations (which you can now do mostly with native JS), jQuery’s $.ajax() method is really handy and works well.

But did you know that this function provides Promise interface out of the box? I recently remembered this and I thought to myself:

Hmm I wonder if I can use async/await with jQuery’s $.ajax().

Turns out, you can!

The setup

Async/await is really new still, it’s only in the ES2017 spec, so you’ll need to use a transpiler like Babel to get it working in older browsers. Most of us are using Babel anyway with our bundlers (Webpack, Browserify), so this isn’t a huge deal.

Assuming you already have Babel installed and configured, the first thing you’ll need to do is get Babel to use the ‘env’ preset. In your .babelrc file, add these lines:

"presets": ["babel-preset-env"],

You’ll also have to install this Babel preset and polyfill from npm: npm i -D babel-preset-env babel-polyfill.

Once that’s done you’ll also need to install this magic plugin for Babel: npm i -D babel-plugin-transform-async-to-generator. This is the key package that lets you use async/await in your code. I should mention that this simply gets Babel to compile the async/await syntax to ES2015 generators, so if you’re not targeting most modern browsers keep that in mind.

The next, and FINAL thing you need to do is use the babel-polyfill module in your code. You can use a Webpack loader if you like, or just include the package in your source files:

import 'babel-polyfill';


Ok, now we’re ready to go. Start up Webpack and let’s start using async/await!

Don’t call me, maybe

Back in the day you had to use $.ajax() like this:

//Function wrapper that confuses alot of devs because async code works differently
function doAjax() {
        url: ajaxurl,
        type: 'POST',
        data: {
            stuff: "here"
        success: function (data) {
            //wacky nested anonymous callbacks go here
            var something_but_not_really = data;
        error: function (jqXHR, textStatus, errorThrown) {
            // Empty most of the time...

    return something_but_not_really

I know when I was a junior dev I had no idea why something_but_not_really was undefined. I had to learn about callbacks a billion times 😬.

But now…

async function doAjax(args) {

    const result = await $.ajax({
        url: ajaxurl,
        type: 'POST',
        data: args

    return result;

And result actually returns the AJAX result. Cool right?

The big benefit of async/await is that it makes asynchronous code appear synchronous. As in, do this thing, wait for it to finish and then give me the result.


Notice anything missing in our new function? Yep, error handling is non-existent. Fortunately, since async/await is essentially synchronous, you can use try...catch()!!!

async function doAjax(args) {
    let result;

    try {
        result = await $.ajax({
            url: ajaxurl,
            type: 'POST',
            data: args

        return result;
    } catch (error) {

And there you have it. Some error catching built in. Now, there’s other ways to handle errors with async/await, but they’re a little more complex.

The other thing to keep in mind now, since we’re returning the result of an awaited function, result will equal a Promise instance. You have 2 options with what you can do with the result.

The first option is to make sure that you use await when calling doAjax() later on.

// Elsewhere in code, inside an async function
const stuff = await doAjax();

The other option is to use the Promise interface and roll that way:

doAjax().then( (data) => doStuff(data) )

Promises aren’t all that bad, and can look cleaner or be easier to work with, depending. I’ve found that using ES2015 classes it’s sometimes easier to use the Promise interface, so YMMV.

But that’s it – go get your $.ajax() using async/await today!

The post Using async await with jQuery’s $.ajax appeared first on 🔥 Database Critical 🔥.

Posted on by:


markdown guide

Good to know that's available, but why not just use fetch?


I'm glad some one brought up fetch()! Fetch is pretty sweet, but I've found it to be less than perfect when you need to modify headers, particularly for authentication.

Out of the box jQuery's $.ajax() will forward any headers currently set on the page. Fetch however is a lot lower level, similar to using XHR directly. That being the case headers, cookies and authentication parameters have to be set manually.

If you're using GET or a simple POST then yeah, fetch() is fine. But if you want to do anything more complex jQuery, or an Ajax library can be easier.

See: swizec.com/blog/waste-hours-fetch-...

The big benefit to using jQuery's ajax over Axios or Superagent is that it's probably already in your browsers cache from another website, so it's the most common sense tool to use.

But yeah, I use fetch when I can... 😃


Or you know, just use fetch + unfetch as a polyfill


Thanks 4 this articule, just that i needed. I Will try yo implement it AND then a respond again.