[BUG] Axios Error - Twitch Component Won't Execute Due to Error

[clarkio]

Describe the bug
Using any of the Twitch components results in the action failing due to an error with Axios. After further investigation of the error I believe it's due to a recent change to the axios package which is noted in this issue in the Axios repo: axios/axios#5142. This seems to require some changes to what's provided in the configuration object to the axios package - specifically the paramsSerializer option. This option requires a new key called encode.

AxiosError
options must be an object

DETAILS
    at Object.assertOptions 

Note: see attached screen shot for error shown in my workflow

To Reproduce
Steps to reproduce the behavior:

1. Add any Twitch component to a workflow
2. Fill in all necessary fields for the Twitch component you chose
3. Test the action using the Twitch component
4. See the error

Expected behavior
Twitch actions to execute requests and return a result

Screenshots

Desktop (please complete the following information):

• Browser: Brave
• Version: Happy to share this but version of what? My browser? If so it's 1.44.112

Additional context
Axios seems to have made an update that's a breaking change based on this issue in their repo:

I believe this function in the pipedream Twitch component code needs to be updated:

pipedream/components/twitch/twitch.app.mjs

Line 53 in bdb6a86

_getParamsSerializer() {

This issue for the Axios docs covers what I believe needs to change: axios/axios-docs#90

Before:

paramsSerializer: function (params) {
    return Qs.stringify(params, {arrayFormat: 'brackets'})
},

After:

paramsSerializer: {
    encode: function(params) {
        return Qs.stringify(params, {arrayFormat: 'brackets'})
    }
},

[dilanmadusankaathukorala]

Hi @clarkio, Thank you for reporting this issue, I am able to recreate it we will prioritize this to be fixed. Please follow this ticket for updates.

[dannyroosevelt]

Thank you so much for the detailed report and breakdown, @clarkio! FYI since it looks like you were in the component code, we're happy to review a PR if you're interested in implementing the fix yourself, otherwise our team will take a look soon.

[clarkio]

@dannyroosevelt thanks and yea I'd be happy to but I see there is a PR open which I'm also happy to see 👍

[dannyroosevelt]

Oops looks like we jumped the gun on it... but it's in the QA queue, so it should be fixed soon!

[clarkio]

No worries. Glad to see it's moving along quickly and will be resolved

@clarkio TestPassed

[clarkio]

This is great to see. Does it mean it's been published to the platform now as well? @Hassan-Abbas-SQA @lcaresia @dannyroosevelt

[lcaresia]

@clarkio Yes, it's published!

[clarkio]

@lcaresia great to hear. Is there anything I need to do in my workflows to get it updated? I noticed the error still showing up when I tried earlier.