State machines are an old concept. They are a proven solution that provides a solid architectural foundation for application processes. In this article, I hope to provide an introduction to what they are and how they can be useful for a modern web or mobile application engineer. We’ll be focusing on one library in particular – xstate – and how it can allow anyone to easily leverage state machines for managing global or component state.
I’m a big fan of Amplify. I’m also a big fan of TypeScript. Amplify is not built with TypeScript, and to use it effectively, sometimes you need to give it a little help, especially when it comes to GraphQL. With the advent of hooks, we can create some nice utilities for ourselves that let us leverage the power of TypeScript with our GraphQL queries. Let’s see what that looks like.
I’ll be assuming familiarity with React and TypeScript, i…
—
Originally posted by Mat Warger on mw.codes April 19, 2019.
New JavaScript frameworks and libraries are created every day. This generates a dilemma: which solution should we use when starting a project?
My web development experience over the last few years has mainly included the AngularJS and Backbone.js frameworks. Angular, jQuery and traditional JavaScript have been in my comfort zone. When I ended up being face-to-face with TypeScript, it felt new, scary, and pretty confusing. I want to make that transition easier for you!
The goal of this post is to provide you an understanding of TypeScript, particularly when you come from an Angular web development background. To do so, we will first give an introduction to TypeScript. We will then discuss the differences between the different versions of Angular & Angular vs. React, with an eye for what you need to know to understand the JavaScript tooling landscape TypeScript plays in. And, lastly, we’ll go through a tangible TypeScript example for a look into syntax & structure.
We have all been there: some new technology comes out and we know it would improve our maintainability. But we can’t use it. We already picked a technology, it is already implemented, and we can’t change it now. We are stuck.
TypeScript does not work like that. TypeScript is JavaScript, and JavaScript is TypeScript. What this means is any existing files you have are compatible with any new file you add.
So why waste time changing if it’s all the same anyway? TypeScript has some great advantages that JavaScript does not. In this blog I will introduce some of those advantages, as well as some troubleshooting tips for if you run into issues when you choose to convert to TypeScript…
Attention: The following article was published over 12 years ago, and the information provided may be aged or outdated. Please keep that in mind as you read the post.UPDATE: Check out the new GitHub project that accompanies this post: TypeScript Modularization Demo. In my last post, I introduced TypeScript, Microsoft’s new offering which layers static typing on top of JavaScript. …
