feat: compute and log build time

[amaaniqbal]

PR Checklist

• The PR title follows our guidelines: https://github.com/NativeScript/NativeScript/blob/master/CONTRIBUTING.md#commit-messages.
• There is an issue for the bug/feature this PR is for. To avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it.
• You have signed the CLA.
• All existing tests are passing: https://github.com/NativeScript/nativescript-cli/blob/master/CONTRIBUTING.md#contribute-to-the-code-base
• Tests for the changes are included.

What is the current behavior?

Build time not shown in ios.

What is the new behavior?

Build time is computed and logged irrespective of OS.

Fixes/Implements/Closes #2998.

[amaaniqbal]

@rigor789 Please have a look at this PR. Currently, I am logging the build time in seconds. Let me know if I should log the build time in ms or some other format.

[rigor789]

Hey @amaaniqbal - seconds is fine, think most tools log in seconds (including fractions) - this looks fine, just want to run this on both ios/android to see it in action, code LGTM 👍

[amaaniqbal]

seconds is fine, think most tools log in seconds (including fractions)

This was my intuition too 😄.

this looks fine, just want to run this on both ios/android to see it in action

Sure, let me know how it works on your end.

[edusperoni]

this throws performance is not defined on our CI build

conext:

  # android list targets

  sudo apt-get update
  sudo apt-get install -y libhybris-utils

  # setting up correct versions of node/npm
  nvm install 14
  nvm use 14
  nvm alias default current

  # update npm to latest
  npm i -g npm semver colors
  npm config set spin false
  npm config set progress false

  # update yarn
  npm i -g yarn

  gem update bundler -N

  echo -e "n\n" | npm i -g nativescript@next
  ns usage-reporting disable
  ns error-reporting disable

[rigor789]

@edusperoni good to know, we can use a different time source I guess, or a polyfill.

It is strange however, because according to the node docs, performance.now has been available since node 8.5

https://nodejs.org/api/perf_hooks.html#performancenow

Do you have more context around the error? Can you try running the CI build with --log trace?

Edit: I think we just need to import { performance } from "perf_hooks";

Added it in fade332 - you can test once the CI releases it.

[edusperoni]

Yes, that fix solves it. I was just testing it locally and import { performance } from "perf_hooks"; is required for it to work on node.

[rigor789]

@edusperoni I tested the above and worked on my end without the import, using node v15.11.0. 😕

[edusperoni]

@rigor789 I'm using node 14, maybe they changed it in 15?