TanStack Store for Applications

[crutchcorn]

While working on #40 it became clear to me that Store has two different primary users:

• Applications
• Libraries (our main usage today)

See, in libraries like TanStack Form/Table, it's really valuable to know when a Derived instance or Effect is triggering a subscribe so we can know exactly when to remove them or add them back.

For applications? Less important.

However, libraries also need to be framework agnostic where most applications are hooked into libraries.

So this is an open-ended question: How do we want to handle this discrepancy?

I don't just mean with these two APIs, either: We need to have a good backing philosophy for our projects to figure out how we want to treat apps that want to use TanStack Store vs libraries that need it.

---

Further, what value add does TanStack Start provide apps? What features are missing today that would be useful in TanStack Store as an app builder?

Let us know below 💖

[ShyroeJB]

In my job, I use tanstack store for our app instead of other solution that we use before, because we need a custom way to do things right for our app.
We have a store inside a react context, and we create one store by feature, the main pain was to redeclare many block of code to do this, so I create a function like a factory who create the store, the provider, and all usefull hooks.
I build a custom store with tanstack store at the core.
It's like a little library for our custom app needs.

But we also refactor other part of the app who needs global store to use tanstack store because we don't want to have many dependencies to do the same things.

For me the main feature that will be usefull is :

• a devtools like tanstack query or tanstack router, to view the content of a store and track all changes in a history.
• a plugin to enable save a part of the store into storage like local storage (for me it's not a priority I do it in my custom store arround tanstack store)

And why we select tanstack store and not other solutions?
It's because of two things, it's just a simple store so we can extend it for our custom needs and the typing with TS is simple.

For the question how to handle app needs and library needs for API design, I agree with the message in the PR, for a library needs I understand the design but for an app perspective if the api is simple to use it's better.

Maybe something like the design is framework agnostic ok, usage inside library like this new Store, new Derived, new Effect, but for app create primitives, link to the framework specific and use under the hood the api for library part => useStore, useDerived, useEffect etc
The useStore already exist and we need to call new Store before that's ok, but for useDerived we can imagine somthing like we pass the deps and function in params and inside it will call the .mount function and all magic to be used inside the specific framework.

[aarjithn]

From an application perspective, using zustand alongside tanstack query / router is quite popular.

Similarly, jotai has a nice wrapper around query - https://github.com/jotaijs/jotai-tanstack-query

tanstack store could be a potential solution that well integrates in this kind of usecase