`Video.Assets.create` doesn't just return asset anymore

I have the following code:

const asset = await Video.Assets.create({
  input: videoUrl,
  playback_policy: 'public',
})
console.info(asset)

While the type definition clearly indicates that Video.Assets.create would resolve to an asset object that looks like this:

{
  "status": "preparing",
  "playback_ids": [
    {
      "policy": "public",
      "id": "OHWwY9L00OoSNAQ7MrtDH00Gal4S01z7wyeszVLIThmbh00"
    }
  ],
  "mp4_support": "none",
  "master_access": "none",
  "id": "H4I300fePrcZs6lJ009m2vyeiLtojQ7u7FESR3CRf3tZY",
  "created_at": "1632108478"
}

Now it resolves to an object that looks like a HTTP response:

{
  "status": 201,
  "statusText": "Created",
  "headers": {
    ...
  },
  "config": {
    ...
  },
  "request": {
    ...
  },
  "data": {
    "data": {
      "status": "preparing",
      "playback_ids": [
        {
          "policy": "public",
          "id": "OHWwY9L00OoSNAQ7MrtDH00Gal4S01z7wyeszVLIThmbh00"
        }
      ],
      "mp4_support": "none",
      "master_access": "none",
      "id": "H4I300fePrcZs6lJ009m2vyeiLtojQ7u7FESR3CRf3tZY",
      "created_at": "1632108478"
    }
  }
}

I’m using @mux/mux-node v3.2.3.

[dylanjha]

Okay - so those issues were not relevant^… but I did get to the bottom of it

The issue is specific to axios 0.21.2 because [there was a regression in that version]. The regression was quickly patched it in 0.21.3. The regression is that our response interceptor was not getting registered. I was able to replicate this and then confirm that 0.21.3 and later do not have the issue

I’m going to go ahead and update our dep from ^0.21.1 to the latest ^0.21.4 and cut a new patch version of mux-node

[hellovietduc]

Thank you!