Is there any interest in converting this library to using `fetch`? about spotify-web-api-node HOT 4 OPEN

I love that people are invested in this! I have opened up PR #492 that accomplishes the goal of replacing superagent while keeping API compatibility with the existing library (and it's well maintained test suite). It's in @thelinmichael's court now to decide what they want to do with this library.

In the meantime, I think I might take my fork, renamespace it to spotify-web-api-fetch and start updating it to meet my code standards (proper Typescript support, vitest, etc.)

from spotify-web-api-node.

@EduardsE so, I got through updating it and using it AND THEN Spotify released an official Typescript SDK without any dependencies. Sadly, all the arguments to the methods are positional instead of easy to use objects, but I would encourage you to check it out. It has middleware and the ability to provide custom fetch methods.

https://github.com/spotify/spotify-web-api-ts-sdk

from spotify-web-api-node.

I love that people are invested in this! I have opened up PR #492 that accomplishes the goal of replacing superagent while keeping API compatibility with the existing library (and it's well maintained test suite). It's in @thelinmichael's court now to decide what they want to do with this library.

In the meantime, I think I might take my fork, renamespace it to spotify-web-api-fetch and start updating it to meet my code standards (proper Typescript support, vitest, etc.)

Any update on this? There are a couple more things this library would benefit from. Like for example I can't find how to use etags

from spotify-web-api-node.

@eligundry thanks for the quick reply, I'll check it out.

from spotify-web-api-node.