chore: switch TS config to references

[droguljic]

Use references to organize TS configuration with following improvements:

• clear separation between different parts of the project
• no need for nested package.json files
• run tests without installing dependencies and building project first

[MiroDojkic]

@droguljic am I getting this right - with this approach, if anything breaks in the build process our tests won't catch it?

[droguljic]

@droguljic am I getting this right - with this approach, if anything breaks in the build process our tests won't catch it?

That is a great observation.
Previous approach had a side effect of checking the build process due to set up with alias, nested package.json and double install command. Also, it would check the build process once changes were merged into trunk, so PR could break build and nothing would be reported.

The intention is to add check build step to the list of jobs that are run on each PR once this is merged.

[MiroDojkic]

@droguljic thanks for explaining. Can you elaborate on the check build step - how would it check the build?

[droguljic]

@droguljic thanks for explaining. Can you elaborate on the check build step - how would it check the build?

Just run the build to see if it passes. We can also provide an option to persist build artifacts to the workspace for later use if needed down the line.