fx – terminal JSON viewer

50

fx – terminal JSON viewer go release fx.wtf
authored by antonmedv 8 days ago | archive
Archive.org Archive.today Ghostarchive
| 17 comments

17

1. 14
  antonmedv 8 days ago | link
  Hey Lobsters,
  
  I’ve rebuilt fx from the ground up and I’m eager to share the improvements:
  
  Handling of large JSON files? Check. 🚀
  
  Enhanced TUI experience with themes. 🌈
  
  Faster JSON navigation using Dig Fuzzy Search (just hit .). 🐾
  
  Comprehensive regex search across the entire JSON. 🔍
  
  Long strings now wrap as they should. 📜
  
  Embracing all things JSON: comments, trailing commas, and streams. ✏️
  
  The entire rewrite focused on speed and usability. If you’ve found fx useful, I’d appreciate any support through GitHub sponsors.
  
  Feedback and thoughts are always welcome!
  1. 3
    
    giann 8 days ago | link
    
    I’m using fx on a daily basis. Great tool and experience using it. Thanks for this!
    1. 1
      
      antonmedv 8 days ago | link
      
      Awesome) Thanks.
  2. 2
    
    asymmetric 8 days ago | link
    
    What’s the difference between this and jq? It seems to be the TUI experience? Might be worth having a comparison somewhere.
    
    Website looks really nice :)
    1. 2
      
      igorclark 8 days ago | link
      
      Seems like the interactive exploration UI is what mostly sets it apart from jq - and also makes it seem similar at first glance to jless - a comparison with that would be interesting too
      1. 2
        
        qmacro 8 days ago | link
        
        I do like fx for what it offers in terms of exploring datasets. Based on your (valid) comment comparing it with jq I’m wondering if you know about ijq which is very much an “interactive jq”, from gpanders here.
        
        https://sr.ht/~gpanders/ijq/
        
        It’s a great tool.
        
        6
        
        wrs 8 days ago | link
        
        It would be great to merge these two concepts — rich JSON navigation with live processing in either jq or JS languages.
        
        Cue someone telling me this has been an Emacs mode for years… :)
  3. 2
    
    pbsds 8 days ago | link
    
    Can I when I’ve navigated to the value i care about extract its path, like I get with gron?
    1. 1
      
      antonmedv 8 days ago | link
      
      Yes. Easy. Just press y and p.
2. 2
  
  fs111 8 days ago | link
  
  I rediscovered fx yesterday (well, github recommended it to me) It’s nice, but I stick to jless for now
  1. 2
    
    simao 7 days ago | link
    
    I also prefer jless, but your link is pointing to a page about berlin ;)
    1. 1
      
      fs111 7 days ago | link
      
      Whoops, here is the correct link https://jless.io/
3. 1
  
  zk 7 days ago | link
  
  Someone I follow on GitHub starred this a couple days ago. Fantastic project!
  
  I found the default key binds also very intuitive. I’m using it for interactive use - I prefer jq for writing filters and getting data out of JSON for shell scripts, but I might have a go at converting some scripts to use fx filters just to see how I like them.
  
  Great work!
4. 1
  nathell 8 days ago | link
  The other day, I found myself in need of visualising a tree of paths, like this:
  
  /one/two /one/three/four /one/three/five /six
  
  I ended up converting it to a JSON with a one-off Python script, and then using fx for the viewing. It worked very well! Thank you for the tool!
  
  (Incidentally, I’ve been writing my own viewer to satisfy my original need more straightforwardly, but that’s still in very early stages.)
  1. 2
    
    peterbourgon 8 days ago | link
    
    See also gron.
5. icholy 7 days ago | link
  
  [Comment removed by author]
6. 1
  icholy 7 days ago | link
  It would be nice if it could handle a sequence of json object like:
  
  { "a": 123 } { "a": 321 }
  
  Right now I’m getting: Unexpected character '{' after root node on node 1.
  1. 1
    
    antonmedv 5 days ago | link
    
    It could but in streaming mode: via dot
    
    … | fx .
    
    But I guess it should be relatively easy to support multiple top level objects.