|
|
|
|
|
by 4lejandrito
981 days ago
|
|
Hi! I checked your tool (https://naprun.dev) and it follows the same philosophy, I like it. However the reasons why I decided to build my own one are: 1. I love building things, I can't help it. 2. I don't enjoy using markup languages mainly because of lack of autocomplete and difficulty to support more complex use cases. By using typescript fetchbook suddenly inherits all it's powers and can be more easily customized. 3. By piggybacking on top of the Request Web API (https://developer.mozilla.org/en-US/docs/Web/API/Request), I don't have to define custom ways to define requests. Also if you know how do fetch on JS/TS you can grasp fetchbook in less than 5 minutes. Oh and fetchbook is also ready to be used in CI, I run tests for fetchbook in GitHub actions, which are actually fetchbook stories themselves. |
|