Setting the auth.storageKey to avoid migration problems

I’ve been a long-term user of Supabase, and as the platform has changed, so have some of the default values when using prebuilt packages. This sounds very generic, so let’s look deeper. If you use any library, it comes with default settings. That also applies to the Supabase JavaScript libraries. In earlier versions of Supabase, the default cookie name was simply supabase-auth-token. Even back then, this cookie name was configurable, but this is what you got if you hadn’t configured it.

So, if you kept the same version of the library in your project, all was fine. But once I updated my code to newer libraries, even though I did everything correctly, it didn’t seem to work anymore in combination with another application we had in the product that was deployed on the same domain – this other application was still using the older library version. So, even though both were implemented correctly...