Skip to content
Basic NPM package for helping on automate releasing of NativeScript Apps
TypeScript JavaScript
Branch: develop
Clone or download
Pull request Compare This branch is 4 commits ahead of holisticon:develop.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
lib
test/e2e
.editorconfig
.gitignore
.npmignore
.nvmrc
.travis.yml
CHANGELOG.md
Jenkinsfile
LICENSE
README.md
package-lock.json
package.json
tns-buildnumbering.js
tns-changelog.js
tns-package.js
tns-release-notes.js
tsconfig.json

README.md

NativeScript Build Helper apple android

Build Status npm version Maintainability Issue Count Dependency Status devDependency Status

This NPM package helps automate the release of NativeScript applications

** CURRENTLY A PRE-RELEASE **

Requirements

  • Node 4+
  • NativeScript 2.5+
  • Git version control
  • fastlane (if automatic upload is need)

Installation

npm install @toolisticon/nativescript-buildhelper --save-dev

Or if you want to use the development version (nightly build), which maybe not stable!:

npm install @toolisticon/nativescript-buildhelper@next --save-dev

Usage

For those who haven't deployed any apps in v2.4 of NativeScript; one of the new features that is turned on by default is SnapShots. Now most the time this is a AWESOME thing, however occasionally this can cause issues. For example I have one app of mine that this crashes at startup when using SnapShots.

Now the docs do list how to disable snapshots; but it is a lot easier for me to find the notes on my own site than trying to figure out which doc has the info.

The environmental variable you need to adjust is: TNS_ANDROID_SNAPSHOT

0 = Force Snapshots off always 1 = Force snapshots on (including in debug mode) Unset = Snapshots only in Release mode

Build Numbering

Use this command to append the build number to CFBundleVersion on iOS and to versionCode on Android:

tns-buildnumbering 42

Advanced Usage

Debugging

If you need to debug the tests use the node-inspector:

npm run debug
node-inspector --web-port=8282

You can then open chrome at http://127.0.0.1:8282/?port=5858 for debugging.

If you want to have verbose logging add NODE_DEBUG=tns_buildhelper_debug:

NODE_DEBUG=tns_buildhelper_debug node tns-buldnumbering
You can’t perform that action at this time.