Fedor Indutny

Yeah, I don't want to change it for exactly these reasons. Good call! Is the benefit of more sound API outweighs breaking changes? It would be better to deprecate it...

I don't mind naming it `modln` instead of `modrn`, and mentioning it in the docs. Would you care to open a PR?

I have no idea. Should we do same renaming for `andln` => `andrn` then? -1 for hex padding. This is going to be hell of a breaking change.

I think it is useful. > Unexpected padding errors have caused countless problems for libraries. Maybe we can make it throw for just `hex`, and accept without padding for base-16?

I think it works only with prime modulo.

I think `package.json` has `buffer: false` in `browser` field now. Does this suffice?

Oh yikes. Bundling is hard 😭

I don't mind!

Yay, all green! :grin:

(This is actually still me, above is my work account)