Alex

You can make it possible to return and throw. Or make a wrapper for catching. And write in the documents that it is recommended to use a return.

It would be possible to use the already existing wonderful rollup and terser, but they only work with js. Should we process the body of the function, and then add...

- https://github.com/fent/randexp.js - not maintained - https://github.com/arcanis/pxeger - not maintained - https://github.com/arh23/strgen-js - not maintained - https://github.com/suchjs/reregexp - unpopular It's all.

See also: https://github.com/google/intermock https://github.com/faker-js/faker https://github.com/boo1ean/casual https://github.com/ngneat/falso https://github.com/g45t345rt/minifaker https://github.com/chancejs/chancejs https://github.com/w3tecch/typeorm-seeding https://github.com/json-schema-faker/json-schema-faker

Also, as an improvement, I would suggest creating a wrapper interface for the ts package to reduce the size and complexity of the code, and create functions with multiple arguments...

Close as completed?

I think he's talking about something similar: https://github.com/samchon/typia/issues/202 https://github.com/lodash/lodash/issues/3172 ```ts type T1 = { a: string; }; type T2 = { b: string; }; const obj: T1 & T2 =...

https://github.com/Hookyns/tst-reflect

Even when jumping to a large number of pages, the speed will be higher, because reading does not start from the beginning, but from the cursor. And after that, the...

Basically, the user goes to the next page, that is, the cursor pagination is used. And you need to use the offset only at the first request and when jumping,...