The spotify-web-api-js package from NPM does not support this out of the box hence we will have to implement our own support for this.
Preferably the user can start the authorization flow through an action within the interface, and then the implementation can handle updating the token by itself. Since we are using a third party library to talk to the spotify api we might want to just implement the refreshing of a token as an exported function or something similar.
We need support for user Authorization within the application for spotify users.
This is done through the Authorization Guide.
The spotify-web-api-js package from NPM does not support this out of the box hence we will have to implement our own support for this.
Preferably the user can start the authorization flow through an action within the interface, and then the implementation can handle updating the token by itself. Since we are using a third party library to talk to the spotify api we might want to just implement the refreshing of a token as an exported function or something similar.