Airstream VS scalajs-react

I recommend you read the section for each of those in the readme here https://github.com/raquo/Airstream

Don't know of any other native (to Scala) solution to state management other than Airstream

You can see one example in https://github.com/raquo/Airstream/pull/60, you'll need to copy the PR code into your own project though (it doesn't touch Airstream internals so it's easy). If you search Laminar gitter room for "websocket" you'll find other third party websocket implementations too (not sure about specific examples)

Then there's scalajs-react, which can be integrated with existing React ecosystem, but it's just sooo compex: macros, 5-6 type parameters, hundreds and hundreds of cryptic types. We decided to stick with TypeScript instead.

Or the OG React Scala.js library: https://github.com/japgolly/scalajs-react

Japgolly has put a ton of time and care into https://github.com/japgolly/scalajs-react which is a complete React binding in scalajs. This paired with something like Diode (https://github.com/suzaku-io/diode) and you get a full frontend solution in scalajs.

We've got server-side rendering with scalajs-react and scala-graal. Here's a tutorial if anyone's interested. What's really cool about scala-graal is that it has some pretty cool caching so that even with dynamic inputs, you can render pages in nanoseconds (as opposed to 10+ or even 100+ ms).

You can use React with Scala.js, and also most other common JS libraries. Or you can use a Scala.js specific library like Laminar, which I haven't tried myself but it looks nice.

I don't have a lot of experience with it, but many seem to be very pleased with it. Interop with JS is good and you can use React and other common JS libraries, but there is also Scala.js specific frameworks like Laminar.

https://github.com/japgolly/scalajs-react is pretty heavily used as well, and fairly active as a project. In short, building it off of that wouldn't be a huge risk over typescript, and might even be a net win in the long run, as you could re-use some stuff from the backend in the front-end.