This is a bit of a hacky workaround and may not 100% eliminate the issue. I already do this with the hosted Vercel instance. For your own Vercel instance, you can setup a simple cron job to ping the endpoint every few minutes or so to prevent cold starts. Your data is updated approximately every day. If it matches the environment variable WARMUP_KEY, then it will go ahead and issue a simple database read request to Firebase to keep it warm. View your most listened tracks, artists and genres and switch between 3 different time periods. Long request times are usually a result of Firebase database cold starts, which can take up to several seconds ( known issue).Īs a workaround, there's an endpoint at /api/warmup?key= which accepts a GET request with a single query parameter key. This is because GitHub proxies images and will timeout requests if they take too long. Sometimes you may encounter an issue where the widget fails to load on GitHub, with a 502 response from. The app will be running at Common issues Widget fails to load on GitHub

Spotify recently played