BxJS - building React app with XState

Поділитися
Вставка
  • Опубліковано 25 сер 2024
  • This is a livestream in "Building X with javascript" series.
    In this livestream I demonstrate how to build a simple React app with XState.
    Project links:
    Discord: / discord
    Facebook: / buildingproductswithjs
    Reddit: / buildingwithjs
    Project sources: github.com/Bui...
    Social media links:
    Follow me on Twitter: / yamalight
    Follow me on Medium: / yamalight
    Follow me on Github: github.com/yama...
    Follow me on Twitch: / yamalight
    Follow me on Facebook: / buildingproductswithjs
    Support my work: codezen.net/su...

КОМЕНТАРІ • 19

  • @arcticspacefox864
    @arcticspacefox864 4 роки тому

    Very cool job Tim, thank you for doin it 👍😁🦄

  • @chuvvyyk
    @chuvvyyk 4 роки тому

    Мое почтение! Очень полезный и бодрый стрим!

  • @georgekalogeropoulos1813
    @georgekalogeropoulos1813 4 роки тому

    Very cool tutorial

  • @akt255
    @akt255 4 роки тому +2

    I have been hearing about it a lot and I can definitely see the advantages of using a well-defined set of states and actions. I will use it in my next project.
    One question: Putting the whole machine in React Context.. is that the standard way of doing it? Does it have any performance downsides?

  • @g-luu
    @g-luu 4 роки тому

    i think angular's ngrx for statemanagement is so robust that they didn't even bother :)

  • @mohammadrasel1271
    @mohammadrasel1271 4 роки тому

    nice

  • @syafiq55555
    @syafiq55555 4 роки тому

    I like the way u code .. btw, what’s the intelisense extension you’re using for your vscode ? It seems to hv a nice type hinting

    • @TimErmilov
      @TimErmilov  4 роки тому

      just the stock stuff with a a couple plugins on top (specifically "npm intellisense" and "path intellisense")

  • @pooyatolideh9527
    @pooyatolideh9527 3 роки тому

    Hey Tim, just wondering what the performance consequences of keeping all the machines within the same object is, specially while using context. Is there a reason why StoryMachine is not spawn in isolation?

    • @TimErmilov
      @TimErmilov  3 роки тому +1

      I think for the majority of use cases - it shouldn't matter too much.
      If you are hitting a specific perf issue with it - there's quite a few discussions on e.g. github on recommended tweaks.

  • @ehsankhorasani_
    @ehsankhorasani_ 3 роки тому

    less is more

  • @sahilmobaidin2312
    @sahilmobaidin2312 4 роки тому

    I believe the project source link is wrong. Anyway thank for the great tutorial.

    • @TimErmilov
      @TimErmilov  4 роки тому

      Whoops! Should be fixed now, thanks for letting me know :)

  • @alii4334
    @alii4334 3 роки тому

    may I ask what kind of terminal you use?

    • @alii4334
      @alii4334 3 роки тому

      it is Fluent terminal, got it.

    • @TimErmilov
      @TimErmilov  3 роки тому +2

      @@alii4334 it's actually Windows Terminal [1] 😅 With zsh as shell and oh-my-zsh as config.
      [1] github.com/microsoft/terminal

    • @alii4334
      @alii4334 3 роки тому

      @@TimErmilov
      It has the same icon!
      can you refer me to a guide on how to add zsh to it?

  • @MrEnsiferum77
    @MrEnsiferum77 4 роки тому

    I can't get it. If something is connected with react like state machine that is how new apps need to be build, otherwise is obsolete.

    • @TimErmilov
      @TimErmilov  4 роки тому

      Stuff like apollo graphql can very much replace xstate (that is - if your API are done using graphql).
      But yeah, that's definitely one of the best ways to do client-side business logic right now :)