Hey there, it’s summer 2022 and I wanted to share some updates on my shell tools for Mac admins.<\/p>\n\n\n\n
No breaking changes or anything huge, but some nice incremental improvements all the same. When the JSONPath spec<\/a> is finalized I’ll give \u2022 \u2022 Both \u2022 \u2022 P.S. All these tools still work in the macOS Ventura beta \ud83d\ude05<\/p>\n","protected":false},"excerpt":{"rendered":" Hey there, it’s summer 2022 and I wanted to share some updates on my shell tools for Mac admins. No breaking changes or anything huge, but some nice incremental improvements all the same. When the JSONPath spec is finalized I’ll give jpt a more considerable under the hood improvement. For now though, I’m pretty happy […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19,37,51,41,53,12,36,39],"tags":[],"class_list":["post-1171","post","type-post","status-publish","format-standard","hentry","category-bash","category-jpt","category-json","category-jsonpath","category-ljt","category-scripting","category-shui","category-zsh"],"_links":{"self":[{"href":"https:\/\/www.brunerd.com\/blog\/wp-json\/wp\/v2\/posts\/1171","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.brunerd.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.brunerd.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.brunerd.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.brunerd.com\/blog\/wp-json\/wp\/v2\/comments?post=1171"}],"version-history":[{"count":13,"href":"https:\/\/www.brunerd.com\/blog\/wp-json\/wp\/v2\/posts\/1171\/revisions"}],"predecessor-version":[{"id":1187,"href":"https:\/\/www.brunerd.com\/blog\/wp-json\/wp\/v2\/posts\/1171\/revisions\/1187"}],"wp:attachment":[{"href":"https:\/\/www.brunerd.com\/blog\/wp-json\/wp\/v2\/media?parent=1171"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.brunerd.com\/blog\/wp-json\/wp\/v2\/categories?post=1171"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.brunerd.com\/blog\/wp-json\/wp\/v2\/tags?post=1171"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}jpt<\/a><\/code> a more considerable under the hood improvement. For now though, I’m pretty happy with tweaking their behaviors to act like you’d expect (print help and exit if no input detected), to get out of your way when you need to debug your scripts (xtrace is now disabled inside them) and to try to understand what you mean when you ask them a question (key path<\/a> queries now accepted). Because the tools and technologies we make should serve us<\/em>, not the other way around. I hope these tools can save you time, energy, sanity or all the above!<\/p>\n\n\n\njpt<\/a><\/code> the “JSON Power Tool” has been updated to v1.0.2<\/a> with all the nice additions mentioned. If you don’t know already jpt<\/code> can parse, query, and modify JSON every which way. It can be used as both a standalone utility as well as a function to be embedded into your<\/em> shell scripts, without any other dependencies. <\/p>\n\n\n\nljt<\/a><\/code> the “little JSON tool” is jpt<\/code>‘s smaller sibling weighing in at only 2k. While it lacks the transformational powers of jpt<\/code> it can easily pluck a value out of JSON up to 2GB big and output results up to 720MB. It has been updated to v1.0.7<\/a> because dang it, even a small script can have just as many bugs as the big ones. Sometimes more<\/em> if you’re not careful!<\/p>\n\n\n\njpt<\/a><\/code> and ljt<\/a><\/code> now accept ye olde NextStep “keypath” expressions to help win over masochists who might still use plutil<\/code><\/a> to work with JSON! \ud83d\ude01 (I kid, I kid!)<\/p>\n\n\n\njse<\/a><\/code>, the “JSON string encoder<\/strong>” does this one thing and does it well. It can be used in conjunction with jpt when taking in arbitrary data that needs encoding only. It’s a svelte 1.4k (in minified form) and runs considerably faster that jpt<\/code>, so it’s ideal for multiple invocations, such as when preparing input data for a JSON Patch document. v1.0.2 is available here<\/a><\/p>\n\n\n\nshui<\/code><\/a> lets you interact with your users with AppleScript but in the comfort of familiar shell syntax! You don’t need to know a line of AppleScript, although it does<\/em> have the option to output it if you want to learn. Save time, brain cells and hair with shui<\/code>, while you keep on trucking in shell script. It has been updated to v20220704<\/a>.<\/p>\n\n\n\n