Typescript

[CedricGuillemet]

• Use tsc for checks and babel to transpile to .js
• port playground scripts to TS
• removed leftover in build.gradle for UnitTests
• fix 1 PG test for readonly assignement
• Keep using UMD modules instead of ES for multiple reasons (consequent changes in babylon.js CI, 1+ minute buildtime for experience.ts, need of a bundler and size of bundles)

[docEdub]

👍 lgtm

[ryantrem]

I think this is a step in the right direction for sure, but I feel like moving to esm packages instead of umd packages is a big part of what would be added value. But maybe I'm thinking too much about specifically having a test app for the Viewer. I suppose I could have a totally separate .ts entry point for that though, and have that one depend on esm packages.

[CedricGuillemet]

@ryantrem we can talk offline about that. Quickly, I've faced some blockers like:

• Babylon.js ES module need to be transpiled for Chakra compatibility
• No modularity / need bundle. experience.js becomes a 26Mb file
• Need heavy work on Babylon.js PR CI to upload ES package snapshot to use with BabylonNative build

[bghgary]

Quick first pass

[bghgary]

@ryantrem we can talk offline about that. Quickly, I've faced some blockers like:

• Babylon.js ES module need to be transpiled for Chakra compatibility
• No modularity / need bundle. experience.js becomes a 26Mb file
• Need heavy work on Babylon.js PR CI to upload ES package snapshot to use with BabylonNative build

@CedricGuillemet Please include me when we talk about this offline.

[bghgary]

nit: Can we use ?? syntax?

[bghgary]

nit: ditto

[bghgary]

Suggested change

	processCurrentScene(test, done, compareFunction);//, renderImage);
	processCurrentScene(test, done, compareFunction);

[bghgary]

I made some changes to the UnitTests folder where the generated .js files are merged to source control. Should we do this same here?