I was banging my head against the wall trying to make Yakbak work for my use case. First off the tapes are in base64 format which makes it really hard to debug the tapes & also this library is not maintained anymore.
I came across a replacement called Talkback which serves the same functionality but was written from scratch by @ijpiantanida! 👏
Hence this led me to replace my mock Yakbak server with Talkback:
Yakbak Cons:
- The tapes were in base64 format - made it hard to debug the request/response
- It would re-record tapes when
x-request-id changed - an unintended side-effect
- Needed express & morgan libraries in addition to yakbak
- Not maintained anymore
Talkback Pros:
- Easy setup - took less than 2 mins to replace Yakbak
- Logging requests by default - even shows whether it served a cached request or is recording a new tape
- Human-readable tapes - you can see the req/res in JSON5 format
- Ability to rename tapes - this is great as you can know exactly what your tapes your doing
Hence if you are considereing Yakbak for your use case, I would highly suggest you checkout Talkback and use that instead.
I was banging my head against the wall trying to make Yakbak work for my use case. First off the tapes are in
base64format which makes it really hard to debug the tapes & also this library is not maintained anymore.I came across a replacement called Talkback which serves the same functionality but was written from scratch by @ijpiantanida! 👏
Hence this led me to replace my mock Yakbak server with Talkback:
Yakbak Cons:
x-request-idchanged - an unintended side-effectTalkback Pros:
Hence if you are considereing Yakbak for your use case, I would highly suggest you checkout Talkback and use that instead.