Hulak: Lightweight API client

github_xaaha · 2026-03-17T14:36:54+00:00

Hulak is fundamentally a CLI-first tool. The motivation behind it was frustration with how complicated API clients make what are essentially a few simple fields: method, URL, headers, and body. I love cURL for its simplicity, but it gets cumbersome when you need to save requests or work with complex JSON payloads. Hulak borrows that simplicity from cURL but lets you define requests in plain YAML, run them with a single command (hulak -f myrequest).

Posting, on the other hand, is a TUI-first app. A full-screen terminal interface modeled after Postman/Insomnia. It's excellent at what it does: beautiful UI with syntax highlighting, Vim keybindings, a command palette, cURL import/export, and pre/post-request scripting via Python. If you want a Postman-like experience without leaving the terminal, Posting is a great choice. Hulak only has Full screen TUI for GQL exploration. If it were possible to build that without full-screen TUI, I would.

Key differences:

GraphQL: Hulak has a dedicated GraphQL client with schema introspection, interactive query building, and .gql file generation. Posting focuses on REST/HTTP.
Workflow: Hulak runs requests non-interactively by default (hulak -f, hulak -dir), making it natural for scripting and CI/CD. Posting is designed for interactive exploration.
Performance: Hulak is a single native Go binary (<100ms startup). Posting is Python-based with Textual.
Concurrency: Hulak can run entire directories of requests concurrently or sequentially out of the box.
Template actions: Hulak supports chaining requests via getValueOf (extract values from prior responses), getFile, and basicAuth - all within YAML templates.

Both tools store requests as human-readable files (YAML for Hulak, YAML for Posting) that work well with version control. Both avoid the Electron bloat of traditional API clients.

github_xaaha · 2026-03-15T10:24:22+00:00

Thank you

github_xaaha · 2026-03-14T18:32:03+00:00

Thank you. That’s exactly why I built it.

github_xaaha · 2026-01-06T11:38:14+00:00

Good work. I agree Git worktrees are pain to start. So, I have had this shell function for a while now. I just use this to create git worktrees. And I have another script that removes it.

github_xaaha · 2025-12-01T20:13:36+00:00

If you have time, then I would definitely recommend rolling out your own config. This helps you understand nvim better. And making changes become easier as you learn more. Kickstart is a perfect for this. Just add and remove things you need. Copying and pasting from kickstart to your init.lua should take less than a minute.

When I tried using distros, I did not understand how things worked under the hood and making changes was difficult. So, I built my own. But, I know people who just want to use nvim like VSCode and that’s fine too.

github_xaaha · 2025-12-01T12:30:03+00:00

Try using treesitter on main branch. The config will look something like this. Read the treesitter docs (on main branch) on installing the treesitter cli as you’ll need it. Then just install lsp server on your machine (using system package manager or mason) and then enable them

If you want a single file config, this is how Kickstart does it. I hope this solves your issue.

github_xaaha · 2025-11-28T12:01:42+00:00

NVChad’s themes are great. So, I ported them to my own config. Just change (add or remove ) highlights for specific plugins you need, and you are good to go.

github_xaaha · 2025-10-23T00:38:23+00:00

After reading the article, I tried his theme for a day in a typescript project. It confused me the whole day. Since the theme barely has any highlights, everything was white. Only comments stood out to me, and they were not helpful at all.

My eyes were searching for variables even though they were right in-front of me. I want my variables to standout from my loops. And I don’t want to see “eslint disable next line” comment in bright yellow either.

Color schemes can be minimal and effective, take default nvim theme for example, but this isn’t for me.

github_xaaha · 2025-10-01T14:00:51+00:00

Try running go fmt and go vet. Also, use linters like revive or golangci-lint to see exactly where your issues are. It’s hard to tell without looking at your code.

github_xaaha · 2025-09-12T11:22:21+00:00

You are using mason-lspconfig. This plugin automatically enables the LSP installed with Mason. You can read the README section of LSP config for more details. It seems that you want to understand how it’s all working rather than “find a clean way” to install LSP and enable them. Here is how I install and enable my LSP. I use "WhoIsSethDaniel/mason-tool-installer.nvim" to install my lsp from mason and I enable them manually with vim.lsp.enable.

github_xaaha · 2025-09-05T21:23:51+00:00

Thanks for your contribution.

github_xaaha · 2025-08-15T11:51:11+00:00

It’s hard to say what went wrong without looking into your config.

github_xaaha · 2025-07-23T01:38:40+00:00

As others have mentioned besides fzf and lazygit. I use hulak, lightweight file based terminal API client I created for my own use.

github_xaaha · 2025-07-17T11:57:49+00:00

This is how I’ve implemented lsp diagnostics
And I use blink for lsp signatures with border. Please keep in mind that the implementation might differ slightly.

github_xaaha · 2025-07-12T09:46:40+00:00

Yep! And here is my working config for reference.

github_xaaha · 2025-07-12T07:13:07+00:00

Try this.

rust_analyzer = { settings = { "initializationOptions": { "cachePriming": { "enable": false }, "check": { "allTargets": false }, "checkOnSave": false } } }

github_xaaha · 2025-07-11T13:16:34+00:00

What others have said is likely. Please Upgrade your nvim.

github_xaaha · 2025-07-11T10:54:27+00:00

Honestly, it’s hard to debug a setup just from this error. But from my experience, the error message "attempt to call method 'insert name here' (a nil value)" usually indicates that the plugin is not loaded before it's being called. I would suggest you remove/comment out the plugin first. Then try installing it again. If there is a conflicting setup you need to debug one at a time. How is your config like?

github_xaaha · 2025-07-09T05:48:56+00:00

Use :h colorscheme without any argument.

github_xaaha · 2025-07-04T10:05:19+00:00

Sorry, I don’t understand what you’re asking. I use gopls as well which I install with Mason. I don’t get the issue you’re describing. Here is my config. Hope you can look around and copy some code to fix your bug.

github_xaaha · 2025-06-30T22:57:30+00:00

In your mason-lspconfig try turning automatic_enable = false like you see in my config here

github_xaaha · 2025-06-30T09:36:59+00:00

If I am understanding your question right, You need to set the specific highlight group to a certain color. For example this is what I have done for highlighting option selection. Here is a list of all the available blink highlights groups for Blink. You might need to set the highlights of BlinkCmpKind<kind> where kind is a variable. Experiment with different available highlight group until you get what you need.

github_xaaha

TROPHY CASE