jnv is designed for navigating JSON,
offering an interactive JSON viewer and jq filter editor.
Features
- Interactive JSON viewer and
jqfilter editor- Syntax highlighting for JSON
- Use jaq to apply
jqfilter- This eliminates the need for users to prepare
jqon their own
- This eliminates the need for users to prepare
- Configurable features via TOML configuration
- Toggle hint message display
- Adjust UI reactivity (debounce times and animation speed)
- Editor appearance and behavior
- JSON viewer styling
- Adjust completion feature display and behavior
- Keybinds
- Capable of accommodating various format
- Input: File, stdin
- Data: A JSON or multiple JSON structures
that can be deserialized with
StreamDeserializer,
such as JSON Lines
- Auto-completion for the filter
- Only supports:
- Hint message to evaluate the filter
Installation
Homebrew
See here for more info.
brew install jnvOr install via Homebrew Tap:
brew install ynqa/tap/jnvMacPorts
See here for more info.
sudo port install jnvNix / NixOS
See package entry on search.nixos.org for more info.
nix-shell -p jnvconda-forge
See here for more info.
pixi global install jnv
# or
cat data.json | pixi exec jnv
# or
conda install jnvDocker
Build
(In the near future, the image will be available on something of registries)
docker build -t jnv .And Run
(The following commad is just an example. Please modify the path to the file you want to mount)
docker run -it --rm -v $(pwd)/debug.json:/jnv/debug.json jnv /jnv/debug.jsonCargo
cargo install jnvExamples
cat data.json | jnv
# or
jnv data.json
# or write current result to stdout on exit (UNIX only)
cat data.json | jnv --write-to-stdout | some-command
# and also output to file
cat data.json | jnv -- --write-to-stdout > result.jsonKeymap
| Key | Action |
|---|---|
| Ctrl + C | Exit |
| Ctrl + Q | Copy jq filter to clipboard |
| Ctrl + O | Copy JSON to clipboard |
| Shift + โ, Shift + โ | Switch to another mode |
Editor mode (default)
| Key | Action |
|---|---|
| Tab | Enter suggestion |
| โ | Move cursor left |
| โ | Move cursor right |
| Ctrl + A | Move cursor to line start |
| Ctrl + E | Move cursor to line end |
| Backspace | Delete character before cursor |
| Ctrl + U | Clear entire line |
| Alt + B | Move the cursor to the previous nearest character within set(.,|,(,),[,]) |
| Alt + F | Move the cursor to the next nearest character within set(.,|,(,),[,]) |
| Ctrl + W | Erase to the previous nearest character within set(.,|,(,),[,]) |
| Alt + D | Erase to the next nearest character within set(.,|,(,),[,]) |
Suggestion in Editor (after Tab)
| Key | Action |
|---|---|
| Tab, โ | Select next suggestion |
| โ | Select previous suggestion |
| Others | Return to editor |
JSON viewer mode
| Key | Action |
|---|---|
| โ, Ctrl + K | Move up |
| โ, Ctrl + J | Move down |
| Ctrl + H | Move to last entry |
| Ctrl + L | Move to first entry |
| Enter | Toggle fold |
| Ctrl + P | Expand all |
| Ctrl + N | Collapse all |
Usage
JSON navigator and interactive filter leveraging jq
Usage: jnv [OPTIONS] [INPUT]
Examples:
- Read from a file:
jnv data.json
- Read from standard input:
cat data.json | jnv
Arguments:
[INPUT] Optional path to a JSON file. If not provided or if "-" is specified, reads from standard input
Options:
-c, --config <CONFIG_FILE> Path to the configuration file.
--default-filter <DEFAULT_FILTER> Default jq filter to apply to the input data
--write-to-stdout Write the current JSON result to stdout when exiting
-h, --help Print help (see more with '--help')
-V, --version Print versionConfiguration
jnv uses a TOML format configuration file to customize various features.
The configuration file is loaded in the following order of priority:
- Path specified on the command line (
-cor--configoption) - Default configuration file path
Default Configuration File Location
Following the dirs crate,
the default configuration file location for each platform is as follows:
- Linux:
~/.config/jnv/config.toml - macOS:
~/Library/Application Support/jnv/config.toml - Windows:
C:\Users\{Username}\AppData\Roaming\jnv\config.toml
If the configuration file does not exist,
it will be automatically created on first run.
Configuration
[!IMPORTANT]
The syntax in TOML configurations
like default.toml was revamped in v0.7.0,
and the configuration shown below reflects the new format.
A migration tool is not provided for this change.
Please manually replace/update your localconfig.tomlto match the new syntax.
[!WARNING]
Depending on the type of terminal and environment,
characters and styles may not be displayed properly.
Specific key bindings and decorative characters may not
display or function correctly in certain terminal emulators.
The following settings are available in config.toml
/* Detailed source-code truncated for AI context efficiency. */