chore: speed up builds

[dyladan]

This PR aims to speed up compilations by running a single typescript process from the root of the project. CI is marginally faster, but local development is drastically faster.

Summary

• Use composite flag in tsconfig to build all packages with a single compile command.
  • Depends on references list in tsconfig. This list is automatically kept up to date using update-ts-references
• version.ts files are now only generated when the version changes
• Backwards compatibility compilation checks are now included as part of the regular build so there is no reason for them to have their own GHA

Additional benefits

• build is a single process now and is much faster than running a tsc process for each package
• tsc --build --watch will now build and watch the whole repo so a change in api will trigger a rebuild and potentially show errors in tracing or other packages.
  • A watch build in a package will have the same behavior only for that package and packages it depends on directly or indirectly.
• npm run compile in a package will build that package and its dependencies, using incremental builds to skip things that don't need to be rebuilt.

[codecov]

Codecov Report

Merging #1748 (deaa021) into master (27a8d45) will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1748      +/-   ##
==========================================
+ Coverage   92.07%   92.09%   +0.01%     
==========================================
  Files         166      166              
  Lines        5593     5593              
  Branches     1199     1199              
==========================================
+ Hits         5150     5151       +1     
+ Misses        443      442       -1     

Impacted Files	Coverage Δ
...emetry-core/src/platform/node/RandomIdGenerator.ts	93.75% <0.00%> (+6.25%)	⬆️

[obecny]

What has happened to version.ts ?

I would create a script that will generate automatically something like references.ts that probably should not be a part of the repo but should be generated during compilation or once before watch or tests. Then it will be a matter of requiring this file here. I would like to avoid a time consuming process which is also error prone and will be hard to remember to do it when you add a new package etc. This for sure can be automated.

How will this work for examples. Currently I can add examples/nameOfExample to lerna.json and it will bootstrap correctly so I can debug all easily. How will this work after it ?

[dyladan]

What has happened to version.ts ?

I'm not done yet, but my goal is to remove the update version on every build which starts a new process and does multiple file read/writes for each of 37 packages. On my machine it's a significant source of overhead. And instead do it as a postversion step or similar. I'm still working on where that will live.

I would create a script that will generate automatically something like references.ts that probably should not be a part of the repo but should be generated during compilation or once before watch or tests. Then it will be a matter of requiring this file here. I would like to avoid a time consuming process which is also error prone and will be hard to remember to do it when you add a new package etc. This for sure can be automated.

The tsconfig.json references are auto-generated by the postinstall script in the root package.json.

How will this work for examples. Currently I can add examples/nameOfExample to lerna.json and it will bootstrap correctly so I can debug all easily. How will this work after it ?

Will work the same way. You just have to make sure the project is built first by running npm run compile.

[dyladan]

Additional benefits:

• build is a single process now and is much faster than running a tsc process for each package
• tsc --build --watch will now build and watch the whole repo so a change in api will trigger a rebuild and potentially show errors in tracing or other packages.
• npm run compile in a package will build that package and its dependencies, using incremental builds to skip things that don't need to be rebuilt.

[obecny]

lgtm,
I think it will be good to add some doc in readme (DEV SETUP for example) explaining

1. what is being generated automatically
2. How should we boostrap / install things now (if they are any differences etc.)
3. If I were to create a new package or add a new node dependency how would that work.
4. What is the typical dev setup / cycle after this change, how can we run a watch for all etc. to be able to debug stuff .

I hope you can address this prior to merge

[dyladan]

lgtm,
I think it will be good to add some doc in readme (DEV SETUP for example) explaining

1. what is being generated automatically
2. How should we boostrap / install things now (if they are any differences etc.)
3. If I were to create a new package or add a new node dependency how would that work.
4. What is the typical dev setup / cycle after this change, how can we run a watch for all etc. to be able to debug stuff .

I hope you can address this prior to merge

@obecny e96e138