fix: added check for document, so redaxios will not break in Node

[AlexandrHoroshih]

Hi!
I'm currently using redaxios in a project with Next.js and found this problem: using redaxios in Node.js leads to ReferenceError because there is no document object in Node.

Axios for this case provides noop functions for non-browser environments: https://github.com/axios/axios/blob/04d45f20911a02e9457db9e9d104aa156e170b11/lib/helpers/cookies.js#L45.

I added a check on the document object so that code with redaxios can be used in the Node.js environment too

@developit, can you review, please?

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[AlexandrHoroshih]

@googlebot I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[developit]

Hi there - this doesn't make redaxios work in Node, it just makes it not error out. You should be using Axios in Node, and only installing the Redaxios alias for browser compilation. In Next you can do this by checking env.ssr.

[AlexandrHoroshih]

@developit Sorry, I'll correct myself:
this will allow redaxios to be used in Next.js, which adds a server side Fetch polyfill (https://nextjs.org/docs/basic-features/supported-browsers-features#polyfills) or in any other Node application with a polyfill for Fetch, or a custom implementation added via the redaxios config.

I think this will greatly simplify the use of redaxios with Next.js

[developit]

Ah! Yes I actually helped with the fetch polyfill, I should have thought of that!

[AlexandrHoroshih]

So, what you think, @developit?

This line of code, where i had added check for document - is the only line that fails in Next.js (i tried it with my forked version).
Being able to use redaxios in any environment that supports Fetch API (like Next.js server-side part) - looks good to me

[developit]

Hey, sorry for dropping the ball on this. I'm okay with the change, just wanted to check on some size tweaks. Hopefully this week!