feat: use babel-plugin-transform-titanium when transpiling

[sgtcoolguy]

JIRA: https://jira.appcelerator.org/browse/TIMOB-27167

Description:
This is a PR to make use of appcelerator/babel-plugin-transform-titanium

The goal here is both during SDK build and app build to pass along options that the babel plugin can use to inline static values or during evaluation of special "defines" or common platform/os sniffing expressions.

Relates to tidev/node-titanium-sdk#131.

During SDK build
This PR makes use of the inlining during our generation of the bundled ti.main.js. You can look into the SDK's dist/tmp/common folders for the bundled ti.main.js to see the effects (though given we run other transpiration and rollup it can be difficult to know what to look for - easiest thing to spot are removed Ti.Platform.name and Ti.Platform.osname sniffing expressions).
This can bake in static constant property values for platforms (think Ti.buildHash, Ti.Platform.osname, Ti.Filesystem.separator), or replace platform sniffing in our common JS code.

During App build
We pass along options through to node-titanium-sdk to specify the target platform, distribution target, deploy type, etc. So at app build time it can replace even more than simple platform sniffing (think Ti.App.* properties).

[build]

	Messages
📖	💾 Here's the generated SDK zipfile.
📖	✊ The commits in this PR match our conventions! Feel free to Rebase and Merge this PR when ready.
📖	✅ All tests are passing Nice one! All 6549 tests are passing. (There are 701 skipped tests not included in that total)

New dependencies added: babel-plugin-transform-titanium.

babel-plugin-transform-titanium

Author: cwilliams

Description: Replace known values in Titanium apps to allow for further simplification via dead code/evaluation in babel minify

Homepage: http://npmjs.com/package/babel-plugin-transform-titanium

Created	about 1 year ago
Last Updated	7 months ago
License	NO LICENSE FOUND
Maintainers	1
Releases	3
Keywords	babel-plugin

README

This is a babel plugin intended to optimize Titanium SDK applications by inlining various static values. Once inlined, Other babel plugins may performa additional optimizations to help strip away "dead code".

Information about the current Titanium application build should be passed to the plugin's options object.

Plugin Options

const options = {
	deploytype: 'development', // one of 'development', 'test', 'production'
	platform: undefined, // one of 'android', 'ios', 'windows'
	target: undefined, // one of 'dist-playstore', 'dist-appstore', 'dist-adhoc', null/undefined
	Ti: {
		version: undefined, // string, SDK version
		App: {
			id: undefined, // string, application id from tiapp.xml
			name: undefined, // string, application name from tiapp.xml
			version: undefined, // string, application version from tiapp.xml
		}
		Platform: {
			osname: undefined, // one of 'android', 'ipad', 'iphone', 'windowsphone', 'windowsstore'
		}
	}
};

Special "defines"

It can:

• replace special OS_* references with boolean values
  • OS_IOS - true iff pluginOptions.platform === 'ios'
  • OS_ANDROID - true iff pluginOptions.platform === 'android'
  • OS_WINDOWS - true iff pluginOptions.platform === 'windows'
  • Useful for if/else guards for platform specific code. Once booleans are inlined the false blocks can be removed.
• replace special ENV_* references with boolean values
  • ENV_DEV and ENV_DEVELOPMENT - true iff pluginOptions.deploytype === 'development' (typically simulator builds)
  • ENV_TEST - true iff pluginOptions.deploytype === 'test' (typically device builds)
  • ENV_PROD and ENV_PRODUCTION - true iff pluginOptions.deploytype === 'production' (typically app store/ad hoc builds)
• replace special DIST_* references with boolean values
  • DIST_ADHOC - true iff pluginOptions.target === 'dist-adhoc'
  • DIST_STORE - true iff pluginOptions.target === 'dist-appstore' || pluginOptions.target === 'dist-playstore'

OS "sniffing" via Ti.Platform.osname

• replace typical "sniff" expressions for iOS/Windows using Ti.Platform.osname with static boolean values
  i.e.

if (Ti.Platform.osname === 'iphone' || Ti.Platform.osname === 'ipad') {
	Ti.API.info('on ios!');
}
if (Ti.Platform.osname === 'windowsstore' || Ti.Platform.osname === 'windowsphone') {
	Ti.API.info('on windows!');
}

Generated by 🚫 dangerJS against 9a11c94

[ewanharris]

This looks good to me. Just one minor nit on the timestamp in prebuild.js differing to Utils.timestamp.

Did a small FR and am seeing values get inlined as expected 🎉

[ewanharris]

The timestamp generated here is different to the one generated by Utils.timestamp (2020/01/06 12:10 vs 1/6/2020 12:10). Does that matter?

[sgtcoolguy]

it may! We should be using the same format in the manifest.json in the SDK as we use in the Ti.buildDate property at runtime (and that value should be the same on either platform). I think that Utils.timestamp basically is what will get shoved into the iOS Ti.buildDate in Obj-c, and will be used for the babel pre-filling. And I think is set to the env var we'll use and prefer above here.

So I think this really only matters for local dev builds, but yeah we should be consistent in our formatting.

I think our unit test doesn't actually verify the format of the value so it's possible we've had iOS/Android differing here for a very long (forever?) time.

[lokeshchdhry]

FR Passed.

Studio Ver: 5.1.4.201909061933
SDK Ver: 9.0.0 local build
OS Ver: 10.14.5
Xcode Ver: Xcode 11.3
Appc NPM: 4.2.15
Appc CLI: 7.1.2
Daemon Ver: 1.1.3
Ti CLI Ver: 5.2.2
Alloy Ver: 1.14.4
Node Ver: 12.13.1
NPM Ver: 6.12.1
Java Ver: 11.0.1
Android Devices: ⇨ google Pixel (Android 10)
IOS Sim: Iphone 11 pro IOS 13.3