How do I install videre.nvim with lazy.nvim?

Use the lazy.nvim snippet from the README, adding dependencies like graph_view_yaml_parser for YAML support; ensure to set options like simple_statusline for easier onboarding.

Does videre.nvim work with YAML files?

Yes, but you need to install the optional graph_view_yaml_parser plugin; once added, videre.nvim automatically detects and renders YAML files as graphs.

How do I edit a value in videre.nvim?

Press 'V' to change a value, but follow the rules: strings must be in double quotes, use null/true/false for keywords, and {} or [] for tables/lists; errors occur for invalid inputs.

videre.nvim vs nvim-tree for JSON files?

videre.nvim specializes in interactive graph visualization and editing of data structures, while nvim-tree is a file explorer; choose videre for data navigation and nvim-tree for file management.

Can I customize the keybindings in videre.nvim?

Yes, the README provides a full keymaps section in options; you can remap actions like expand from 'E' to other keys for personal workflow preferences.

Is videre.nvim good for large JSON files?

It has collapsible units and max_lines settings to manage complexity, but terminal rendering may slow down with very large datasets, so test performance for your use case.

videre.nvim

MITLua

A JSON explorer plugin for Neovim that renders structured data as an interactive graph in the terminal interface.

GitHub

140 stars3 forks0 contributors

What is videre.nvim?

videre.nvim is a Neovim plugin that provides a graphical explorer for JSON, YAML, TOML, and XML files directly within the terminal. It algorithmically renders data structures as collapsible, navigable graphs to address the lack of native tree-view visualization in Neovim.

Target Audience

Neovim users who work with structured data files like JSON, YAML, TOML, or XML and want to visualize and navigate them as interactive graphs without leaving the terminal.

Value Proposition

It uniquely brings rich, interactive data exploration to Neovim's terminal interface, offering features like inline editing, customizable styles, and multi-format support through optional parser plugins, all while adhering to a terminal-centric philosophy.

Overview

JSON explorer using Neovim's terminal interface.

Use Cases

Best For

Visualizing and navigating complex JSON or YAML configuration files in Neovim.
Exploring API response data stored in JSON files directly within the terminal editor.

Related Projects

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub

Editing structured data (adding, deleting, modifying keys/values) in a graphical tree interface in Neovim.

Working with TOML configuration files (like those in Rust projects) using a collapsible graph view.

Experimentally viewing XML files as navigable graphs in Neovim with optional parser support.

Managing large data structures by collapsing sections and jumping between linked units for better focus.

Not Ideal For

Users who require high-fidelity, graphical tree views with icons and colors (like desktop GUI tools such as JSON Crack).
Projects where data files are primarily edited in web-based or collaborative environments outside the terminal.
Scenarios involving extremely large data sets where terminal rendering might lag or become unwieldy.
Developers who prefer minimalist Neovim setups and avoid plugins with multiple optional dependencies.

Pros & Cons

Pros

Algorithmic Graph Rendering

Automatically generates visual graphs for data structures using ASCII art, as shown in the README's preview, making complex JSON/YAML files navigable directly in the terminal.

Interactive Navigation

Supports jumping between linked units, setting any unit as root, and traversing with customizable keybindings like 'L' for link_forward, enhancing data exploration without leaving Neovim.

Multi-Format Support

Works with JSON (built-in), YAML, TOML, and XML via optional parser plugins, though XML support is experimental and requires xml2lua.nvim.

Inline Editing

Allows adding, deleting, and modifying keys/values directly within the graph interface, with specific rules such as strings must be wrapped in double quotes for consistency.

Cons

Experimental XML Support

XML parsing relies on an external, experimental plugin (xml2lua.nvim), which may be unstable, poorly maintained, or limited in features compared to JSON support.

Strict Editing Rules

Editing values requires strict syntax adherence, like wrapping strings in quotes and using only null/true/false keywords, which can be error-prone and less intuitive for quick edits.

Dependency Heavy for Non-JSON

Support for YAML, TOML, and XML requires installing separate parser plugins, adding setup complexity and potential maintenance overhead beyond the core plugin.