Erik Söhnel

@BasixKOR could you please rebase on the latest master - I have removed node 12, the benchmarks now run on 14, 16 and node 18 only so your PR should...

> 'should throw on missing attributes' test is breaking though Could you skip that benchmark then? It is okay if you only implement the benchmarks that deepkit supports. I created...

@jsoldi looks like you forgot to run the actual benchmarks with `npm run start`? That will run all cases, write the results to `docs/results`, which is then shown in the...

Hi @dimatakoy yeah its well alive. I am using it in production myself. The merged PRs which have not been released are breaking changes to the API. I wanted to...

Planning? Not really but better support for (simple) JSON conditions sounds like a good addition. Do you have any specific use-cases in mind? I for myself am only using Postgres...

Of course! Atm. the build and packaging is completely done with tsdx but that has not seen an update in years. Any suggestions on how to replace tsdx with something...

You're right, this is missing. Wasn't a priority for me as I've never encountered a recursive type in any API that I needed to validate. Do you happen to have...

Thx, that looks good. Is it just something that is missing in theory or do you have a case at hand where you need this feature? I know that filesystems...

@jeengbe have you tried running the tests with `npm run test` - what do they say? If a benchmarked library does not implement the benchmark correctly (e.g. raises an exception...

:+1: also at the bottom of the benchmark graph there is a short description what every benchmark is supposed to test: https://moltar.github.io/typescript-runtime-type-benchmarks/