Yesterday we released a new version of the NativeScript Webpack plugin that includes some non-trivial changes. In this article we’ll walk you through why we made these changes, and what you’ll need to change in your apps to upgrade.

In NativeScript Core applications, a common pattern to support two-way data binding is to create a view model that extends NativeScript’s own Observable. By using Observable’s get() and set() methods, we get UI updates for free. Unfortunately, these methods accept magic strings to let the API know what property name was updated. With the help of TypeScript, we can solve this problem!

In this article I’ll tell you how I build NativeScript apps. One of the great things about NativeScript is you have a lot of flexibility in how you build, so you can find a workflow that works for you. Let’s look at how I build.