proposal to remove version-update script during build

[mayurkale22]

Here is the performance comparison w/ and w/o version-update script during the bootstraping process (npm run bootstrap). I believe version-update script is only needed before publishing the new version, which means no need to run during every build process.

w/ version-update script	w/o version-update script
real 2m31.442s	real 1m16.299s
user 3m21.372s	user 1m45.918s
sys 0m19.538s	sys 0m11.541s

Either we can update the RELEASING.md document to run script when we prepare the package for new version or manually change the version.

[dyladan]

Wow that is a much bigger difference than I would have guessed. What OS are you on? Could be an odd filesystem caching issue or even AV software that slows down the process because of file accesses? Maybe we could make it so that the version is checked as part of a custom linting rule rather than as a separate custom script.

[mayurkale22]

macOS Mojave

[dyladan]

I'm seeing similar performance impact on catalina. Maybe we should include this as part of a release automation.

[OlivierAlbertini]

Also for each job on circleci, we generate js files with tsc... I’m wondering if we could cache them in order to be reuse by other jobs. In this way, we compile only once

[obecny]

I had similar issue with AVG - just try to turn it off and see if you can still see so big difference. If this won't be the case anymore then I guess the issue is the antivirus.

[dyladan]

Unfortunately, most of us are on work computers which require AV and backup software. Just disabling it isn't an option for me and I suspect others.

[obecny]

I didn't mean to disable this forever, just disable that and test if that change anything or not.

[mhennoch]

I think this is fixed, possibly by #1748? @dyladan