Cordova 5.1.1 and plugin updates

June 10, 2015 Cordova 5.1.1 released (previous version was 5.0). Such a delay in publication is due to the fact that it was not immediately possible to complete the work with the Russian translation. Most of the changes in this version were minor improvements rather than significant improvements. About a week ago on June 22, 2015. also an update for the main plugins.

For those who are interested in what was done, please ask under the cat.

The main innovations were:

• Support for Windows 10 applications
• Added new requirements command
• Improved support for cordova prepare --browserify
• The release of a new patch version of the platform is now possible without re-release of tools.

And now a little more:
')

Support for Windows 10 applications

Earlier in Cordova, it was possible to develop applications only for Windows 8.0 and Windows 8.1. Now, as the new version of Windows is just around the corner, the appearance of tools that will make it possible to prepare for this release is very favorable. In Windows 10, a new application launch mode has appeared, and Cordova applications are subject to security policy changes. More information about the changes in Windows 10 can be read in the official documentation .

Also, Windows 8 is declared obsolete platform, and gradually its support will come to naught.

Also in Windows 10 applications, you can use CSP to restrict access to resources, and this makes it easier to run some Javascript libraries that did not work with safeHTML restrictions.

Added new requirements command

Now, before adding a platform to a project, you can see which requirements are not met on the computer. Previously, you just had to call the cordova platform add android and try to decrypt what you lack for development. Instead, it is now enough to call cordova requirements android and see the list of requirements.

Very convenient for beginners, I think. And note that in order for the team to work, you need to use the latest version of the platform. So they will have to update them, with new projects, of course there should be no problems.

Improved support for cordova prepare --browserify

Now you can use cordova prepare --browserify with third-party plugins to form cordova.js. For those who do not know, cordova prepare --browserify allows cordova prepare --browserify to collect all the JS files of plug-ins into one single file, and thus avoid the dynamic loading of these files when the application starts.

The release of a new patch version of the platform is now possible without re-release of tools.

This innovation means that the delivery of versions of platforms with a modified number of the patch version will be carried out without the need to update command line tools. Each new application will thus receive a more updated version of the platform. Now the version of the platform that is installed when creating the application is strictly protected in the command line tools, which, when a security update appeared, required not only the patch to be corrected, but also the toolkit update so that it did not install an unprotected platform version.

Now about plugins

In short, the main changes

cordova-plugin-battery-status - added support for the browser platform.
cordova-plugin-file-transfer - various bugs fixed

Despite the fact that in the official release there is a huge sheet with a list of works, this mainly concerns the updating of documentation and the finalization of automated tests for plug-ins. What the end developer is not very interesting.

If you have any comments on the work of the latest versions of Cordova, you can write a ticket to JIRA . Those who wish to help with the transfer can register at CrowdIn and help with the translation .