Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@holisticon/nativescript-buildhelper

Package Overview
Dependencies
Maintainers
2
Versions
226
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@holisticon/nativescript-buildhelper

Basic NPM package for helping on automate releasing of NativeScript Apps

  • 0.3.1
  • latest
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
248
increased by1671.43%
Maintainers
2
Weekly downloads
 
Created
Source

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 @holisticon/nativescript-buildhelper --save-dev

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

npm install @holisticon/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=holisticon_tns:

NODE_DEBUG=holisticon_tns node tns-buldnumbering

Keywords

FAQs

Package last updated on 01 Nov 2018

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc