We’re excited to announce the v5 beta release of XState and related packages after many years of development.
The search results in the Stately Studio and XState docs are now context-aware. So if you’re browsing the current XState V4 version of the docs, you’ll get results for V4, and if you’re browsing the XState V5 beta version of the docs, you’ll get results for V5.
Sometimes you want to share a machine with descriptive details or comments, so we’ve added annotations to Stately Studio.
Over the week we made the following improvements.
Tomorrow is part four in our popular Stately Stream series, where we are modeling a semi-complex client-side app using XState, Stately Studio, React and TypeScript. You can catch up on the previous videos in the series below or watch all our past videos in our Stately Streams YouTube playlist.
Two weeks ago, we had what some have called our “best office hours yet.” We introduced a whole bunch of new features and improvements to Stately Studio, including state.new with our new starter machine, annotations, embed mode, and version history. We also gave the first peek at our most significant editor update to date; we call it “codename: blocks,” check out the video to find out why!
It’s been more than six months since the release of Stately Studio 1.0, and we’ve been busy working on Stately Studio and XState. Here are some of the highlights:
Our top priority at Stately is to make it as easy as possible to create robust app logic in the form of state diagrams. That’s why we’re constantly striving to remove any potential barriers.
Today we’re happy to introduce another pro feature for our Stately Studio subscribers; Version History. With this feature, you can save versions of your work as you go and refer back to them in the future.
There’s now a more detailed default machine when you create a new machine in Stately Studio or when you jump straight into modeling at state.new.