Status of the Project? about spotify-web-api-node HOT 9 OPEN

There is a new TS SDK for the web API now: https://github.com/spotify/spotify-web-api-ts-sdk

from spotify-web-api-node.

ref: https://community.spotify.com/t5/Spotify-for-Developers/spotify-web-api-node-seems-abandoned/m-p/5454468#M6976

from spotify-web-api-node.

@Xiphe I am wondering the same thing . . . I see some things being added via PRs that I would love to have access to!

from spotify-web-api-node.

This looks interesting: https://community.spotify.com/t5/Spotify-for-Developers/OpenApi-Swagger-description-for-the-Web-API/td-p/5196705

from spotify-web-api-node.

Ended up replacing this library with a manually generated client from Spotifys Open API spec using oazapfts

oazapfts --optimistic https://developer.spotify.com/_data/documentation/web-api/reference/open-api-schema.yml ./spotify.api.ts

Unfortunately, the auth flows are not part of that spec so I'll need to do that "by hand" but I can live with that as long as I have up to date methods & response types

from spotify-web-api-node.

@Xiphe awesome! could you create a repo for this?

from spotify-web-api-node.

@jpcastberg What would you hope to find in that repo?

from spotify-web-api-node.

@Xiphe I ended up using the spotipy python library to do my project, was mainly looking for easy auth flow handling. If you're going to be adding better auth support in your openapi node library, it may be useful to others.

from spotify-web-api-node.

The problem is spotify auth goes over a differen API which is not part of their OAS spec. So there's nothing oazapfts (or similar generators) can do about it.

from spotify-web-api-node.