Question 1

How to install rest.nvim with lazy.nvim?

Accepted Answer

Add the plugin to your lazy.nvim config with dependencies for nvim-treesitter to ensure tree-sitter-http is installed. No .setup() call is needed; configure via vim.g.rest_nvim for customization.

Question 2

rest.nvim vs Postman: which is better for API testing?

Accepted Answer

Choose rest.nvim if you prefer staying in Neovim with fast, scriptable requests and deep editor integration. Postman is better for GUI features, team collaboration, and cloud-based collections.

Question 3

Can I use JavaScript scripts in rest.nvim?

Accepted Answer

Yes, by default scripts are parsed as JavaScript to match the HTTP spec, but you can specify Lua with # @lang=lua for more flexibility and integration with Neovim's Lua ecosystem.

Question 4

How to manage cookies in rest.nvim?

Accepted Answer

Cookies are automatically saved and loaded between requests via a configurable file path. Enable cookie support in the configuration and use :Rest cookies to edit the file directly.

Question 5

Does rest.nvim support GraphQL requests?

Accepted Answer

It can handle HTTP requests, so you can send GraphQL queries in the body, but there's no built-in GraphQL-specific syntax highlighting or validation, unlike specialized tools.

Question 6

How to set environment variables from a .env file?

Accepted Answer

Use commands like :Rest env select to choose a .env file, which is automatically loaded based on patterns. Variables can be dynamic and reused across requests for testing scenarios.

rest.nvim

What is rest.nvim?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Open Source Alternative To

Frequently Asked Questions