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

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: https://github.com/axios/axios/issues/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: https://github.com/PipedreamHQ/pipedream/blob/bdb6a86866a4400dbee0cdb487b783473dcbfe01/components/twitch/twitch.app.mjs#L53

This issue for the Axios docs covers what I believe needs to change: https://github.com/axios/axios-docs/issues/90

Before:

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

After:

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

[dannyroosevelt]

FYI we’ve identified the issue and confirmed it’s not related to this Twitch update. We are tracking the issue re: not getting prompted to update existing actions here.

[clarkio]

@dannyroosevelt oh whew ok that sounds much better. However I did just manually update by removing some steps and re-adding them and it’s working now. I’ll use what you suggested @dannyroosevelt to update other workflows using this component.