[v2] AbortController is not defined on @uppy/aws-s3-multipart when SSR

When importing @uppy/aws-s3-multipart on a SSR situation (Nuxt) the error AbortController is not defined is thrown

[onhate]

So, this library (and fix) not meant to be run on node.js, it just allows the server side bundle to not fail when generating the HTML for the client, I don’t think a polyfill is needed as it will never run on Server Side, instead just the check if variable it not undefined is more than enough to allow it to work.

[aduh95]

I’m inclined to reconsider polyfilling AbortController if it isn’t supported on latest LTS without a flag. What do you think?

For the record, it was decided not to polyfill this: AbortController is available on all the browsers Uppy officially supports, it wouldn’t make sense to add a polyfill to fix an issue that doesn’t affect a supported environment. Instead, we decided to land https://github.com/transloadit/uppy/pull/3169 to fix the ReferenceError on environments that do not have AbortController and AbortSignal globally available; although users of such environments should be aware that they might encounter other errors if the code is trying to use those API, and they should consider upgrading to an environment that does support it (such as Node.js 16.x), or polyfill it themselves.