Field-level request/response encryption middleware for TypeFetch ↗ contracts — AES, DES, RSA, Base64, or your own handlers.
npm i @tahanabavi/typefetch-encryptionWhy it is a separate package
It used to ship inside @tahanabavi/typefetch, which meant every consumer
installed crypto-js and node-forge whether or not they encrypted anything.
Moving it out is what lets the core declare zero runtime dependencies — the
first thing an enterprise audit checks, and not a claim you can make with two
crypto libraries in the tree.
The contract side did not move. encryption is still a key on an endpoint, and
EncryptionMethod / DeepEncryptionMap / EncryptionConfig are still exported
from typefetch core, because they are types with no runtime cost. You can declare
an encrypted endpoint without installing this package; you just cannot execute
one.