Juan Carlos

[Workaround, pull requests welcome.](https://github.com/juancarlospaco/nodejs/tree/main/tools) 🙂

I think `varints` can be replaced by a new `bigints` on stdlib, then stdlib remains kinda constant in size.

I was thinking `varints` suppose to be a bigint kinda thing but was never completely implemented, sorry.

Maybe some inspiration can be D stdlib BigInt ?: https://dlang.org/phobos/std_bigint.html I think competitive programming is an example use case, but maybe others benefit too, like Scientific Nim projects.

Haskell comes with BigInt now.

This needs a switch, can break Testament tests that check output.

I dont remember but investigate this, it should allow to customize stacktrace messages without breaking the compiler and all tests: https://nim-lang.github.io/Nim/stackframes.html#setFrameMsg.t%2Cstring%2Cstring Maybe you can improve it.

I dunno, I discovered by accident when coding a feature to download ebooks on https://github.com/juancarlospaco/biblioteca-guarrilla#biblioteca-guarrilla Tiny ZIP are Ok, but big ZIP fail, ZIP are not corrupted anyways.

Near ~10 Mb I think, I try to adjust the provided files as much as I can. I didnt try with non-zip files, I dont know. I dont know enough...

```nim $ nim c -r -d:useStdLib hello.nim Hint: used config file '/home/juan/.choosenim/toolchains/nim-0.19.0/config/nim.cfg' [Conf] ../../.nimble/pkgs/jester-#head/jester.nim(1261, 9) Hint: Synchronous route `match` has been optimised. Use `{.async.}` to change. [User] Hint: [Link] Hint:...