stepci VS vim-http-client

Location: EU, Germany

Remote: Yes

Willing to relocate: Yes

Technologies: HTML, CSS, TailwindCSS, JavaScript, TypeScript, Node.js, React/Next.js, Vue/Nuxt, GraphQL, REST, Postgres, Git, AWS, Docker + K8s

GitHub: https://github.com/mishushakov

LinkedIn: https://linkedin.com/in/mishushakov

Email: hey at mish.co

Most recently, I worked at Step CI a Technical Founder and authored the API-Testing Framework (https://stepci.com) and Garph (https://garph.dev), a full-stack API-Framework, which brings the developer-experience of tRPC to GraphQL.

My passion is in making tools developers love using and make them more productive.

For automated testing, you should give Step CI (https://github.com/stepci/stepci) a try

Ps. I helped build it

The problem is that you can import commonjs modules in ESM but not the other way around. For stepci (https://stepci.com) we have chosen to not support ESM for this very reason. We want that the library “just works” for all our users

Hopscotch is not a Postman fork as far as I know.

You can also do request chaining with Step CI (https://stepci.com) and Hurl (https://hurl.dev)

There’s also Step CI: https://stepci.com

Disclaimer: I’m one of the authors

It's a config driven uptime monitoring service powered by Step CI, an open source API testing framework.

You might try DiY-ing it with this open-source framework - https://stepci.com/

If you are using vim, you could try this one https://github.com/aquach/vim-http-client. I have been using it for some time and it has worked well. Use in your local file system, integrates well with vim but I had to fork it since it didn't had a timeout setting.

I have moved from postman to https://github.com/aquach/vim-http-client and have never looked back ever since, its opens in vim and has variables to store values and can store comments too in a .txt file. Give this a try if you are using vim.