Spotify-Readme icon indicating copy to clipboard operation
Spotify-Readme copied to clipboard

A dynamic, customizable, and real-time Spotify now-playing widget that seamlessly integrates with your website or GitHub markdown files!

Results 27 Spotify-Readme issues
Sort by recently updated
recently updated
newest added

I've had this weird, weird bug and I thought I'd bring it up as I can't find any details about it anywhere else. I've forked your repo and made some...

bug

**In my function log vercel** ![image](https://user-images.githubusercontent.com/98865315/165153495-1aa6f4ba-c69d-42ef-a444-266696a2f7b8.png) and when i visit my url with `/api` [myspotify-nqbill.vercel.app](https://myspotify-nqbill.vercel.app/api) ![image](https://user-images.githubusercontent.com/98865315/165154111-3d5dda2e-a514-42ec-87a8-d782c88c2a84.png) please help @itstommi

Hi, I deployed the repo on vercel and when i'm going on the endpoint /api i get this error ![image](https://user-images.githubusercontent.com/54556960/162596845-011e7ec3-41e7-42b2-9ccd-13f1d1625fc9.png) ![image](https://user-images.githubusercontent.com/54556960/162596848-898fa9ec-5bb9-4494-997d-7ec6eeef6ccc.png)

After deploying on Vercel I see this error. I tried revising my vercel.json to be this: ``` { "rewrites": [ { "source": "/(.*)", "destination": "/" } ], "headers": [ {...

question

[ERROR] Runtime.ImportModuleError: Unable to import module 'vc__handler__python': cannot import name 'url_quote' from 'werkzeug.urls' (/var/task/werkzeug/urls.py) ![500](https://github.com/tthn0/Spotify-Readme/assets/65740751/23c6b195-8383-42fa-8462-f7e023dccbe3)

bug

Hello dev! First of all, thank you for this project that looks and run great. I have an enhancement request : the card would auto refresh on song change so...

enhancement

`Fixed 500: INTERNAL_SERVER_ERROR` `[ERROR] Runtime.ImportModuleError: Unable to import module 'vc__handler__python': cannot import name 'url_quote' from 'werkzeug.urls' (/var/task/werkzeug/urls.py) Traceback (most recent call last): ` #### The error was encountering is due...

the access token have a lifetime of 3600s, so why not cache them rather than creating new access tokens at every request?

enhancement

Werkzeug 3.0.0 was released and Flask doesn't specify the dependency correctly (requirements says Werkzeug>=2.2.0). This is why, Werkzeug 3.0.0 is still installed and Flask 2.2.2 isn't made for Werkzeug 3.0.0....