You can now open your machine in CodeSandbox or StackBlitz. These options show when you select either JavaScript or TypeScript export formats in the Code panel. When you open your machine in these external editors, it will be deployed as a demo app so you can jump quickly into prototyping and get an example of how to integrate your machine into your codebase.
The Stately team has had another busy week. The editor now has event schemas, and we’ve made many more improvements. Let’s dig in!
Yet another new Pro feature for you this week: you can now lock machines to prevent accidental edits. Lock a machine using the lock icon button in the machine Details panel.
This week, the Stately team has been hard at work with even more bug fixes and improvements.
You can now choose to export state and event descriptions and meta fields with your exported code.
Our new Learn Stately guidance got its own changelog this week, but there’s more that’s new to Stately.
We’ve just released a new way for new users to learn Stately. We know that the learning curve is one of the biggest challenges you face when adopting state machines in your teams. We’ve designed our Learn Stately guidance and accompanying tutorials to introduce the basic concepts of state machines, demonstrate how to build them, simulate them, export them to code, and implement them with the exported code.
We have more fixes and improvements for you this week.
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.
🤫 We’re testing a new feature where you can embed machines.
From the Share menu, there’s now a Copy embed URL button. You can use this URL in an <iframe> to embed your machine anywhere <iframe>s are allowed. We love to use embedded machines in our docs!
We plan to add more to this feature in the future, and we’d love to hear your feedback.
