The error looks like it's coming from a dependency used by supertokens (tough-cookie) and apparently has some history in that project. Curious if you all run into that when testing. link to their github issue if you're curious: https://githubcom/salesforce/tough-cookie/issues/215

As far as I can see supertokens doesn't use tough-cookie. It's used by jsdom and request (and maybe some others) which are a dev dependencies of our library. Since they are only dev dependencies they shouldn't install for you when you install supertokens in your project. Anyway, we haven't come up on this issue, we do most of our testing (of auth-react) in browser through puppeteer.

You could try setting up your jsdom environment with a different URL (we use "localhost.org" in some tests)

You could also try adding a custom

cookieHandler

into the supertokens config. Using that you should be able to fully customize how we handle cookies, you could even make it use localstorage or some kind of in-memory thing completely circumventing tough-cookies

I can't find a guide about this in our docs, but: this is a function that should return an object with two props: - getCookie: by default this returns

document.cookie

(basically a string of the format

cookieName1=value; cookie_name2=value...

) - setCookie: by default this takes a string parameter and assigns it to

document.cookie

. (this saves it into the cookie list, the format of the string is something like

cookiename=value; cookieSettings...