I am super excited to announce the immediate availability of NativeScript 2.5! The NativeScript team worked hard to deliver a solid and feature-rich release that adds even more value on top of our framework.
In order to do an even better job of demonstrating some of the high value features in this release, we put together a NativeScript 2.5 video for you:
Let us know in the comments if this kind of a release presentation resonates with you!
Be sure to read these instructions on updating NativeScript.
Now on to the details of NativeScript 2.5:
Support for WebPack 2.0: Bundling your code with webpack is now easier and more extensible than ever. The nativescript-dev-webpack plugin now uses webpack 2.0 and allows you to freely modify your webpack config. We have also added numerous small improvements like:
The minification feature has been on our roadmap for quite some time, but it required shipping changes to several components. You can now trigger a minified build by passing the --uglify
flag to your build/run npm script. Of course, all Uglify options can be fully customized by configuring the UglifyJsPlugin
in your webpack config.
Ahead of Time (AoT) Compilation: When you install the nativescript-dev-webpack
plugin, it comes with the AoT compiler enabled for Angular 2 applications.
For this release we have enabled debugging in Chrome DevTools! This includes debugging plain JavaScript as well as TypeScript. For Android this is the default experience when you run the tns debug android
command, while for iOS it is exposed behind a flag: tns debug ios --chrome
. The reasoning behind this difference is that the existing AppInspector integration (which is a modified version of the Safari DevTools) provides much richer functionality for iOS than Chrome. As we continue to expose features in the Chrome DevTools that are already available in AppInspector, we will consider making Chrome the default option at some point.
As a side note - because it will technically difficult to enable all the features (such as profilers and timeline) of AppInspector in Chrome DevTools for iOS, we’d love to know what's the added value of having Chrome DevTools versus the existing AppInspector. Sound off in our comments section below!
Besides the numerous bug fixes, there are several improvements over the current CLI behavior. The tns run <platform>
command, for example, now automatically enables the livesync -- watch
behavior. This is something that the entire team considers less confusing and much more straightforward during the development life cycle.
We are also deprecating support for Node.js 4.x and now require support for Node.js LTS 6.x. For more information on the behavior of the development workflow commands you may follow this wiki.
The debugging experience when using the Visual Studio Code extension is now even better! The newly introduced watching behavior of the default launch commands makes the process of editing, deploying, and debugging the app faster than ever before. The feature was initially added in v0.5 of the extension with the name Sync on iOS/Android
. In the new v0.6 it is enabled by default in the Launch on iOS/Android
command and the old Sync on iOS/Android
has been removed. If you want to learn more about the way it works check out the docs article.
The latest version of UI for NativeScript is out to the public as well and features a brand new Gauges component, a further polished and more customizable DataForm control, and an improved AutoCompleteTextView component. For more information you can read the separate announcement blog post for UI for NativeScript.
The NativeScript demo application for iOS and Android, developed exclusively by the engineering team to showcase the capabilities of NativeScript, got some fresh new updates.
It will feature push notifications with updates on the latest from NativeScript as well as blog posts and a "What's new" section available under the sidebar menu. It will also feature two new samples on the DataForm component, part of UI for NativeScript. You will see the updated version in the app stores very soon.
Our QAs are doing an incredible job in securing stable releases along the road. They have actually developed an entire framework that we'd like to share with you, hoping you will find it useful when you create automated tests for your NativeScript applications!
Among the key features worth mentioning:
More hands-on samples and usage may be found here.
The "starter" application that we use to generate the NativeScript Code Samples section in our docs also received several valuable new additions:
As always, we have big plans for our next release. Be sure to keep an eye on our public roadmap for updates. You can also impact our roadmap by sounding off on our ideas portal!
In the meantime, you can get up-to-the-second information through a variety of outlets: