spotify-web-api-node VS Immer

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.

```

It looks like it’s mutating, but both the reducers and update() uses immer* under the hood, so we still respect immutability under the hood.

Cami supports redux devtools so you can use that for time-travel debugging too!

—-

* https://github.com/immerjs/immer

I heard that immutability libraries like immer.js [0] help with this. Anyone go this way and had good success? Is this 'the way'?

[0]: https://immerjs.github.io/immer/

So, that's what we built, and we built it in the most obvious way — using JavaScript Proxy objects to track mutations and reflect those changes across Appsmith’s framework. Initially things looked good — it worked, aside from a few hacks to make some data types work with map and set, and we were following the example of other projects that had similar requirements. If it was good enough for them, it should be good enough for us, right?

But is immer really the ultimate answer? The performance problem of immer is more prominent in large arrays and deep-level object scenarios. See this issue description, many authors in the community began to try to make breakthroughs, and noticed that structura and mutative, I found that it is indeed many times faster than immer as they said, but it still fails to solve the problem of both fast speed and good development experience. I will analyze the two issues in detail below.

I like immer for this kind of thing: https://github.com/immerjs/immer

It gives you immutable updates without getting bogged down in FP abstractions.

I've always been a huge fan of immer for these case. For your code, it would simply turn into setGridData((prev) => produce(prev, draft => applyChanges(changes, draft)) but I recommend you go over their documentation to fully understand how it works

If you're trying to make things actually immutable, Object.freeze and deep copies can clutter things up pretty good, have you considered using something like immer? (https://immerjs.github.io/immer/)

If you want to set up from Context, Zustand is your best bet. It offers an extremely simple API that lets you create a store with values and functions. Then, you can access that store from anywhere in your application to read and write values. Reactivity included! If you want to store nested object data in your store, consider using Immer alongside Zustand to easily change nested state.