#xstate — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #xstate, aggregated by home.social.
-
Just launched Unfortunate Transitions 👻
A little puzzle game where you're a poltergeist eliminating your cheerful housemate through indirect means. Built with #XState code visible in-game.
-
HDD - Happiness Driven Development.
Over past few days I've been struggling to try to wedge #xstate library into my next project. I love the idea of state machines, I adore the tooling, I would love to see it everywhere for it's reasoning and academic cleanness.
But I decided to cut it out from the project and just use pure #EmberJS (tracked + services + ember-concurrency).
Resons? Selfish, really.
- EmberJS already has native tooling to solve vast amount of cases in way more elegant manner that xstate can.
- The interweaving of Ember & xstate just does not have great DX and I ended up writing tons of obscure code to do trivial mutations or derived state checks.
- While the xstate visual machine editor is cool, I find it lacking / buggy, so I end up going back to the code, which is, frankly, not easy to read.
- It might be the learning curve, but really what I can write in 5mins in pure EmberJS takes me hours in xstate (counting in fighting with TS gods).Overall give xstate a try. State Machines feel like the correct way to go for things. But for me the DX of xstate is not there. I chose high HDD.
-
#XState looks like a very cool tool for handling complex state in react apps with a visual editor to help build and understand the state transitions, setup and exit side effects. https://xstate.js.org/
Only for VSCode unfortunately.
2/3 -
jotai-xstate v0.5.0 has been released! It finally migrates to XState V5. Huge thanks to the contributors!
Now, we may need to update the docs and examples. Would anyone like to volunteer?
-
-
🆕 Don’t put off migrating from XState v4 to v5 any longer!
Kevin has created a detailed step-by-step guide to walk you through migrating your machines from beginning to end:
https://stately.ai/blog/2024-02-02-migrating-machines-to-xstate-v5
-
C’est parti pour le meetup Front-end & Beers ! On commence avec la conférence d’Antoine Richard qui nous parle de #XState.
-
- What did we tell you?
- To not build "state machines by hand"...
- And what did you do?
- I build a state machine by hand ...
- And what is the outcome?
- Pain and frustration in trying to hunt down hard to debug edge cases...
- So what do you do next time?
- If it's really really small can I ...
- No! No! Nooooo! -
🎥 @laura explains the actor model & how it relates to state machines, in simple terms:
-
I've started a little #typescript experiment library (unpublished as of right now) to develop a better, more strongly typed state machine library than #xstate. It's not really in a usable state right now--without context it's pre-MVP--but it's already quite promising imo.
https://blog.martijnarts.com/p/e48ad6bf-689e-4dc8-b77c-07b2fe358098/
-
🎉 New episode of JS Party!
Amal, @nicknisi & special guest @laura geek out over the remarkable growth and evolution of the #XState project and its team in recent years 🥳
Laura also tells everyone about Stately, a SaaS platform that uses AI to create seamless state management solutions compatible with various tools like XState, #Redux & #zustand 💽
-
🙋 Do you use XState + React?
Make yourself known in the State of React 2023 survey! XState is under State Management 😊
https://survey.devographics.com/en-US/survey/state-of-react/2023 #XState #stately #stateMachines #statecharts #react #stateOfReact2023
-
⏮️ Watch David as he makes an XState V5 cheatsheet for our docs. Featuring plenty of examples and some extra time on Vue compatibility…
-
@b0rk https://xstate.js.org/viz/ is an interactive playground for statecharts/state machines. #xstate
-
When using #XState in #EmberJS, state-machines *are* components.
Completely transparent integration.
Docs: https://github.com/NullVoxPopuli/ember-statechart-component
-
Playing with #XState for a take-home test and found an interesting issue related to testing:
The official docs just mention "send the events and eventually the test will pass", but actually it won't. You need to manually wait for the state to change and then trigger the successive events, otherwise it won't progress. Which goes against their own beliefs, so I wonder if that's a bug.
Published an example here: https://gist.github.com/marcoacierno/2246fc9d66c5aa5449fee91ee772ff11
-
Implemented a (#xstate compatible) custom state machine+reducer combination for a #React app and finally it worked out.
1st app (~1 year ago) -> complete failure, I deleted everything
2nd app (~6 months ago) -> codebase got more confusing and harder to maintain but running
3rd app -> I could solve exactly the issues I hoped I could, the app runs much better and its easier to improve & add new features 🥳
Should also be easy to reuse when another app could benefit from it. -
I wrote a blog post about #statecharts #statemachines and #xstate https://tritarget.org/#How%20I%20understand%20state%20machines
-
ember-statechart-component makes statecharts are first class citizen.
Statecharts *are* components.
✨A totally transparent integration 🥳
Supports Glint to!
-
#XState (the library) and #Stately (the company) are two things I'm very excited about these days. State machines have so many uses: front end, back end, workflows, parsers...
The stuff Stately is doing make them easy to build and understand. And XState has an extremely small footprint at runtime.
Anyway, their office hours are on now: https://www.youtube.com/watch?v=MpbbgOQ9WAI
-
Refactoring some of my old code and realising how many times did I re-invent what #xstate gives me for free.
Very much recommended for every developer out there: https://xstate.js.org/ -
Spent an #OSS hack day building a serverless #xstate demo. We've had an approximation of this architecture in production at OVO for a while now, excited we can finally open source a part of our implementation.
It allows you to write state machine based serverless apps in #TypeScript :typescript:
Code coming soon 👀
