revenut-web VS nanostores

One side effect my SaaS[1] experienced with card testing is that Stripe's reporting still includes this fraudulent activity as successful which throws off my numbers. For those who can relate, I documented it on GitHub[2] and even developed a mobile app (PWA) that corrects the issue with Stripe's mobile app reporting.

[1] https://last10k.com

[2] https://github.com/hbcondo/revenut-web

Same here, I was using Draw.io but just did a sequence diagram showing a Stripe integration in Mermaid.js on a GitHub readme:

https://github.com/hbcondo/revenut-web#-workflow

But that diagram just renders as code for the same readme via GitHub Pages:

https://revenut.com

I specifically selected Expo / React Native + Typescript for its Authentication library[1] that allowed me to easily integrate Stripe's web login[2]. Expo apps can also be exported as PWAs using Workbox[3] so you could have your app distributed by yourself and have a native version in the app stores

[1] https://docs.expo.dev/develop/authentication/

[2] https://github.com/hbcondo/revenut-web#-authentication

[3] https://developer.chrome.com/docs/workbox/

In its docs, Astro recommends nanostores, but I’ve used effector in the past. And LOVED IT. So I’ve used it for this project as well.

Nanostores explanation

vidstack is very light on technical details but starts with a concise intro and a screenshot, as well as relevant links: https://github.com/vidstack/player

payload is well-structured in general: https://github.com/payloadcms/payload

nanostores starts out with an intro and telling code examples, followed by lots of technical details: https://github.com/nanostores/nanostores

Nanostores and Reatom are also great, fast atomic libs

Astro handles multi-framework components (React, Vue, etc) and they recommend using the nanostores library for shared state.

Checkout Nanostore it's what Astro.build recommends for sharing state across different ui libraries.

All of these are valid ways of fixing the state management issue, but it's clear that we need to find a common solution that works for all the UI libraries. This is where nanostores comes into play! The description they provide on their GitHub page is simply perfect:

Jotai and Valtio are both also really good. Recently looked at Nanostore as well and has some similarity to Jotai and Recoil.

Just to chime in on framework agnostic stores, Astro.build recommends using Nano Stores to handle reactivity, as the base library is very small and they have adapters for most relevant frameworks. I definitely agree that avoiding framework lock-in is the smart thing to do.