Dominik Picheta

You can already make use of libraries like [nim-jwt](https://github.com/yglukhov/nim-jwt) fairly easily from Jester (there is at least one other library for this too). If you want middleware then you can...

Not really sure we can do much here in jester, it's more of a Nim limitation. You can `export json` in api.nim to work around it.

AFAIK `nimble path` returns the path to the source code, which seems correct for what you got.

At this point, why don't we just make `nimble bump` an alias to `bump`? Better yet, Nimble should have the ability to delegate functionality to executables named `nimble-` so `bump`...

> We could just execute bump in the shell if nimble is provided bump arguments or perhaps a bump subcommand? Yes, again, I'd like a generic solution where packages can...

> "Every command must start with nimble-" doesn't add any usability whatsoever. Huh? It obviously adds usability, it would make these kinds of features trivial.

> @dom96 - main push back from me is that nimble bump is longer than bump This push back doesn't make sense to me. If ``nimble bump`` works (by calling...

> Much easier pathway than building new functionality or integrating bump directly into the core of nimble. Your thoughts? If that question is aimed at me then you should already...

So I've hidden some comments that have gone off-topic, please create separate RFCs for those. **You might be surprised, but I do actually love this idea.** There are still some...

I've just been going through the issues and wondered: while we're adopting this RFC could we also adopt [scoped org packages](https://internals.rust-lang.org/t/scoped-packages-like-in-npm/10223/3)? i.e. ``nimble install dom96/jester``. Even if we don't adopt...