Don't use a filepath ending in .js, let the require implementation
resolve the js file. This makes it easier to require the correct
platform-specific file when bundling by switching the webpack
`resolve.extensions` setting.
Add android definitions to check if they will get downloaded
Set the language to android
Attempt starting the app
Add a new redirection to the testapp-runner - a runOnly verb
Disable the install prompt
Enable the buildOnly- and runOnly- commands
Fix the version of the packages
Comment cleanup code. Workflow to be reworked
Install android 23 to make the app build
Build the test app with the @next android runtime
Add @next ability. Build with it
Specify oracle java version 8
Use switcher to switch to oraclejdk8
Switch to a single step so that build breaks on first failure
Reorder attempting to use higher nodejs
Attempt using node 5.10.1
Detect test failure
Add detection for test failures
Decrease verbosity
Extract the test checkers to a separate script
Unignore the build folder recursively. Add the fixed script
Remove the redundant node-version messages
Run the tests with Api level 21
The grunt file respected the --leavecomments option, used when
generating the How-To articles of the API Reference. This was broken with
the passthrough option to grunt-ts.
- tns-core-modules-base.d.ts containing modules definitions with as little
platform stuff as possible. Angular apps will reference this one.
- tns-core-modules.es6.d.ts adding some platform stuff to base. Intended to
be used in environments supporting ES6 (obviously)
- tns-core-modules.d.ts adding to the previous one definitions for our ES6
polyfills: promises, collections, weakmaps, etc. The usual reference point
for most apps.
- Generate a combined tns-core-modules.d.ts file for user projects. (Will
be included in tsconfig.json files by the `tns` tool automagically.)
- Test the integrity of the generated combined file by compiling it.
- Remove all traces of the obsoleted tns-definitions package.
