Synchronising changes from js-logger

[emmacasolin]

Description

Updating CI/CD including:

• Continuous benchmarking
• Staging branch
• Advanced type checking

Tasks

• 1. Create new staging branch
• 2. Synchronise changes from js-logger

Final checklist

• Domain specific tests
• Full tests
• Updated inline-comment documentation
• Lint fixed
• Squash and rebased
• Sanity check the final build

[emmacasolin]

Should the benchmarks here be changed to be done continuously in the CI/CD (like js-logger) or be left as is? @CMCDragonkai

[CMCDragonkai]

Yea benches should be migrated over to the same style. It's fairly easy to copy, similar index.js and more.

[CMCDragonkai]

Should update all the package.json dependencies to match.

[CMCDragonkai]

I'll run the benchmarks here, so you can move on to other libraires.

[CMCDragonkai]

I'll need to add this into codesee too after you merge it.

At the same time... try generating the docs as well, and squash it all.

[CMCDragonkai]

And the scripts all require executable permission.

[CMCDragonkai]

It looks like ts-node using swc fails to run the benchmarks because the decorator plus symbol properties are not being compiled properly. Disabling and removing swc makes the benchmarks work again. This may be related to swc-project/swc#5189.

So for this project we'll need to switch off the usage of swc. But this creates a problem, any benchmarking for PK which relies on the async-init will end up not working. We will need swc upstream to be fixed.

[CMCDragonkai]

I posted a linked bug here TypeStrong/ts-node#1844.

So for now swc could affect any benchmarks running in ts-node too... Basically any call ready wrapped functions. Be wary of this, you may wish to disable the swc: true in those other repos. But we will keep swc where we can until we can make use of it.