spotify-web-api-node VS graphql-js

It looks like that SDK is specifically meant for browsers. In the Spotify Web API Libraries list, they list spotify-web-api-node as the only library under node.

One of my favorite libraries demonstrating the builder pattern in practice is spotify-web-api-node.

The answer is, yes, it's possible. Unfortunately the answer to where to begin is to learn to code. You would need to learn: - a programming language. Let's say you choose to learn javascript. - the general concepts of a REST API and packages/libraries in the language of your choice as you will need to use these - The Spotify REST API to control Spotify and enable syncing the lights. You could optionally use a Spotify API wrapper for your language of choice to simplify this. - A library to control your lights.

But yeah it's basically just Feed the artist name into Spotify search Make sure the artist is a good match Select their top two tracks Add the tracks to the playlist I’m using this https://github.com/thelinmichael/spotify-web-api-node - you just have to be careful with being rate limited by Spotify which is based on the number of requests you make over a 90 second period, and the total number over a 24 hour period.

To begin, I'm going to start with GraphQL. This repo is a JS-specific implementation for GraphQL, for which projects written in JS/TS can utilize to build an API for their web app. The reason why I chose this project is because I've always been intrigued by how GraphQl challenges the standard way of building an API, a.k.a REST APIs. I have very little knowledge about this project since I've never used it before at work or for my personal projects. I only have theoretical knowledge about it which I gained from watching YouTube videos. It also uses TypeScript which is fascinating because type safety is very important when building software considering it cleans out a lot of bugs early on before the software is shipped.

When I asked this in StackOverflow over a year ago I reached the solution of using graphql + graphql-zeus.

In short, we chose not to pursue GraphQL due to some limitations with union types and a lack of support for maps. This is further detailed in this link: limitations.

benchmarks: This directory contains benchmark tests that help measure the performance of the package's code, these tests can be are very useful when experimenting with performance optimizations, and to ensure no slowdowns are introduced between releases. Example from graphql.

GraphiQL (and many other tools) relies on introspection query which AFAIK is not guaranteed to have any specific order (and many libs don't support it). Apollo Server is built on top of graphql-js and it relies on it for this functionality.

GraphQL.js + Knex.js + knex-types (TypeScript generator for Knex)

Yoga v2 supports some experimental GraphQL features such as @defer and @stream, allowing you to get a taste of the future of GraphQL (with compatible clients such as URQL).

Visitors are used for many reasons like extensibility, plugins, printing an entire schema somewhere, etc.

support for @defer and @stream