And you also might want to add xstate to the "state" section: xstate.js.org/
It allows to write state machines to mange the app flow in addition to work as a state holder (in the context). At work we started using it a lot lately and have greatly reduced the size of our react components. The business logic moved into xstate and with the visualizer, it's always all clear how the app came to its current state and how it can go from there.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The daily.dev plugin is awesome. Thanks a lot!
And you also might want to add xstate to the "state" section: xstate.js.org/
It allows to write state machines to mange the app flow in addition to work as a state holder (in the context). At work we started using it a lot lately and have greatly reduced the size of our react components. The business logic moved into xstate and with the visualizer, it's always all clear how the app came to its current state and how it can go from there.