Login with Google, Discord, Twitch only work if the associated social login provider is available. This typically requires access to an API key and, therefore, does not work for the opensource local deployment build (i.e. ./b data-snapshot run). However, on http://localhost:3000 (the splash page for the local build) the social logins are still listed, and do nothing or crash the web server when clicked.
Desired solution
Conditionally render the social logins based on whether the social login provider is available. A brute-force approach would be to not show the social logins if using the data-snapshot build.
Overview
Login with Google, Discord, Twitch only work if the associated social login provider is available. This typically requires access to an API key and, therefore, does not work for the opensource local deployment build (i.e.
./b data-snapshot run
). However, onhttp://localhost:3000
(the splash page for the local build) the social logins are still listed, and do nothing or crash theweb
server when clicked.Desired solution
Conditionally render the social logins based on whether the social login provider is available. A brute-force approach would be to not show the social logins if using the
data-snapshot
build.