fx
jp
Our great sponsors
| fx | jp | |
|---|---|---|
| 50 | 6 | |
| 18,490 | 716 | |
| - | 1.8% | |
| 9.2 | 1.1 | |
| 9 days ago | 11 months ago | |
| Go | Python | |
| MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
fx
- Bash/Zsh autocomplete for JSON fields
- Fx 32.0, now with YAML support too
- Fx JSON viewer now supports YAML
-
Jaq – A jq clone focused on correctness, speed, and simplicity
There's also this awesome tool to make JSON interactively navigable in the terminal:
https://fx.wtf
- Fx 31.0.0 Release
- FLaNK Stack Weekly for 30 Oct 2023
- jq 1.7
-
Modern Linux Tools vs. Unix Classics: Which Would I Choose?
Using awk/sed to parse json seems to be using the wrong tool for the job.
As an alternative to jq with easier to remember syntax, see https://fx.wtf/
Recent discussion: https://news.ycombinator.com/item?id=37567009
- Fx – Terminal JSON Viewer
- fx – terminal JSON viewer
jp
-
Jq Internals: Backtracking
I have a hard time suggesting such a thing, because I find JMESPath incredibly inferior to jq's expressiveness, but if you're in the AWS ecosystem much, you may enjoy https://github.com/jmespath/jp#readme which uses the same query language as does awscli (https://docs.aws.amazon.com/cli/latest/userguide/cli-usage-f...). That may at least pay more dividends than keeping jq's language in your head where it will only ever be used by jq
-
using JQ to parse output
Have you tried this utility instead: https://github.com/jmespath/jp
- Zq: An Easier (and Faster) Alternative to Jq
- What tools did you discover that made your work so much easier for DevOps & SRE
-
FX: An interactive alternative to jq to process JSON
There’s also jp, which interprets JMESPath: https://github.com/jmespath/jp
This one has the advantage of being natively understood by aws-cli, meaning you can pass a JMESPath to an AWS call and only receive the filtered / transformed result back.
- Tips on Adding JSON Output to Your CLI App
What are some alternatives?
jless - jless is a command-line JSON viewer designed for reading, exploring, and searching through JSON data.
jq - Command-line JSON processor
jiq - jid on jq - interactive JSON query tool using jq expressions
jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]
jid - json incremental digger
jet - CLI to transform between JSON, EDN, YAML and Transit using Clojure
rq - Record Query - A tool for doing record analysis and transformation
scout - Reading and writing in JSON, Plist, YAML and XML data made simple when the data format is not known at build time. Swift library and command-line tool.
kubectl-jq - Kubectl plugin that works like "kubectl get" but runs everything through a JQ program you provide
ngs - Next Generation Shell (NGS)