{ "componentChunkName": "component---src-templates-issues-tsx", "path": "/issues/213", "result": {"data":{"issuesJson":{"id":"7447670a-f8ac-5368-ae38-aa299be84735","title":"tomnomnom/gron: 将 JSON 转换为离散的值，以使其更易于根据需要进行 grep 并查看其绝对路径","number":213,"bodyHTML":"

\n

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Repos	tomnomnom/gron
Views	$\"views\"$
Stars	$\"stars\"$
Forks	$\"forks\"$
License	$\"license\"$
UpdatedAt	$\"last-commit\"$
CreatedAt	$\"create-at\"$

\n\n

\n

\n

\n

gron

\n

\n

Make JSON greppable!

\n

gron transforms JSON into discrete assignments to make it easier to grep for what you want and see the absolute 'path' to it.
\nIt eases the exploration of APIs that return large blobs of JSON but have terrible documentation.

\n

▶ gron \"https://api.github.com/repos/tomnomnom/gron/commits?per_page=1\" | fgrep \"commit.author\"\njson[0].commit.author = {};\njson[0].commit.author.date = \"2016-07-02T10:51:21Z\";\njson[0].commit.author.email = \"mail@tomnomnom.com\";\njson[0].commit.author.name = \"Tom Hudson\";\n

\n

gron can work backwards too, enabling you to turn your filtered data back into JSON:

\n

▶ gron \"https://api.github.com/repos/tomnomnom/gron/commits?per_page=1\" | fgrep \"commit.author\" | gron --ungron\n[\n  {\n    \"commit\": {\n      \"author\": {\n        \"date\": \"2016-07-02T10:51:21Z\",\n        \"email\": \"mail@tomnomnom.com\",\n        \"name\": \"Tom Hudson\"\n      }\n    }\n  }\n]\n

\n

\n
Disclaimer: the GitHub API has fantastic documentation, but it makes for a good example.
\n

\n

Installation

\n

gron has no runtime dependencies. You can just download a binary for Linux, Mac, Windows or FreeBSD and run it.
\nPut the binary in your $PATH (e.g. in /usr/local/bin) to make it easy to use:

\n

▶ tar xzf gron-linux-amd64-0.1.5.tgz\n▶ sudo mv gron /usr/local/bin/\n

\n

If you're a Mac user you can also install gron via brew:

\n

▶ brew install gron\n

\n

Or if you're a Go user you can use go install:

\n

▶ go install github.com/tomnomnom/gron@latest\n

\n

It's recommended that you alias ungron or norg (or both!) to gron --ungron. Put something like this in your shell profile (e.g. in ~/.bashrc):

\n

alias norg=\"gron --ungron\"\nalias ungron=\"gron --ungron\"\n

\n

Or you could create a shell script in your $PATH named ungron or norg to affect all users:

\n

gron --ungron \"$@\"\n

\n

Usage

\n

Get JSON from a file:

\n

▶ gron testdata/two.json \njson = {};\njson.contact = {};\njson.contact.email = \"mail@tomnomnom.com\";\njson.contact.twitter = \"@TomNomNom\";\njson.github = \"https://github.com/tomnomnom/\";\njson.likes = [];\njson.likes[0] = \"code\";\njson.likes[1] = \"cheese\";\njson.likes[2] = \"meat\";\njson.name = \"Tom\";\n

\n

From a URL:

\n

▶ gron http://headers.jsontest.com/\njson = {};\njson.Host = \"headers.jsontest.com\";\njson[\"User-Agent\"] = \"gron/0.1\";\njson[\"X-Cloud-Trace-Context\"] = \"6917a823919477919dbc1523584ba25d/11970839830843610056\";\n

\n

Or from stdin:

\n

▶ curl -s http://headers.jsontest.com/ | gron\njson = {};\njson.Accept = \"*/*\";\njson.Host = \"headers.jsontest.com\";\njson[\"User-Agent\"] = \"curl/7.43.0\";\njson[\"X-Cloud-Trace-Context\"] = \"c70f7bf26661c67d0b9f2cde6f295319/13941186890243645147\";\n

\n

Grep for something and easily see the path to it:

\n

▶ gron testdata/two.json | grep twitter\njson.contact.twitter = \"@TomNomNom\";\n

\n

gron makes diffing JSON easy too:

\n

▶ diff <(gron two.json) <(gron two-b.json)\n3c3\n< json.contact.email = \"mail@tomnomnom.com\";\n---\n> json.contact.email = \"contact@tomnomnom.com\";\n

\n

The output of gron is valid JavaScript:

\n

▶ gron testdata/two.json > tmp.js\n▶ echo \"console.log(json);\" >> tmp.js\n▶ nodejs tmp.js\n{ contact: { email: 'mail@tomnomnom.com', twitter: '@TomNomNom' },\n  github: 'https://github.com/tomnomnom/',\n  likes: [ 'code', 'cheese', 'meat' ],\n  name: 'Tom' }\n

\n

It's also possible to obtain the gron output as JSON stream via
\nthe --json switch:

\n

▶ curl -s http://headers.jsontest.com/ | gron --json\n[[],{}]\n[[\"Accept\"],\"*/*\"]\n[[\"Host\"],\"headers.jsontest.com\"]\n[[\"User-Agent\"],\"curl/7.43.0\"]\n[[\"X-Cloud-Trace-Context\"],\"c70f7bf26661c67d0b9f2cde6f295319/13941186890243645147\"]\n

\n

ungronning

\n

gron can also turn its output back into JSON:

\n

▶ gron testdata/two.json | gron -u\n{\n  \"contact\": {\n    \"email\": \"mail@tomnomnom.com\",\n    \"twitter\": \"@TomNomNom\"\n  },\n  \"github\": \"https://github.com/tomnomnom/\",\n  \"likes\": [\n    \"code\",\n    \"cheese\",\n    \"meat\"\n  ],\n  \"name\": \"Tom\"\n}\n

\n

This means you use can use gron with grep and other tools to modify JSON:

\n

▶ gron testdata/two.json | grep likes | gron --ungron\n{\n  \"likes\": [\n    \"code\",\n    \"cheese\",\n    \"meat\"\n  ]\n}\n

\n

or

\n

▶ gron --json testdata/two.json | grep likes | gron  --json --ungron\n{\n  \"likes\": [\n    \"code\",\n    \"cheese\",\n    \"meat\"\n  ]\n}\n

\n

To preserve array keys, arrays are padded with null when values are missing:

\n

▶ gron testdata/two.json | grep likes | grep -v cheese\njson.likes = [];\njson.likes[0] = \"code\";\njson.likes[2] = \"meat\";\n▶ gron testdata/two.json | grep likes | grep -v cheese | gron --ungron\n{\n  \"likes\": [\n    \"code\",\n    null,\n    \"meat\"\n  ]\n}\n

\n

If you get creative you can do some pretty neat tricks with gron, and
\nthen ungron the output back into JSON.

\n

Get Help

\n

▶ gron --help\nTransform JSON (from a file, URL, or stdin) into discrete assignments to make it greppable\n\nUsage:\n  gron [OPTIONS] [FILE|URL|-]\n\nOptions:\n  -u, --ungron     Reverse the operation (turn assignments back into JSON)\n  -v, --values     Print just the values of provided assignments\n  -c, --colorize   Colorize output (default on tty)\n  -m, --monochrome Monochrome (don't colorize output)\n  -s, --stream     Treat each line of input as a separate JSON object\n  -k, --insecure   Disable certificate validation\n  -j, --json       Represent gron data as JSON stream\n      --no-sort    Don't sort output (faster)\n      --version    Print version information\n\nExit Codes:\n  0\tOK\n  1\tFailed to open file\n  2\tFailed to read input\n  3\tFailed to form statements\n  4\tFailed to fetch URL\n  5\tFailed to parse statements\n  6\tFailed to encode JSON\n\nExamples:\n  gron /tmp/apiresponse.json\n  gron http://jsonplaceholder.typicode.com/users/1 \n  curl -s http://jsonplaceholder.typicode.com/users/1 | gron\n  gron http://jsonplaceholder.typicode.com/users/1 | grep company | gron --ungron\n

\n

FAQ

\n

Wasn't this written in PHP before?

\n

Yes it was! The original version is preserved here for posterity.

\n

Why the change to Go?

\n

Mostly to remove PHP as a dependency. There's a lot of people who work with JSON who don't have PHP installed.

\n

Why shouldn't I just use jq?

\n

jq is awesome, and a lot more powerful than gron, but with that power comes
\ncomplexity. gron aims to make it easier to use the tools you already know, like grep and sed.

\n

gron's primary purpose is to make it easy to find the path to a value in a deeply nested JSON blob
\nwhen you don't already know the structure; much of jq's power is unlocked only once you know that structure.

","updatedAt":"2025-05-21T16:00:52Z","upvoteCount":null,"author":{"login":"eryajf","avatarUrl":"https://avatars.githubusercontent.com/u/33259379?u=e4a4090a38ac2473aaed4ef9945233636776c6c3&v=4","url":"https://github.com/eryajf"},"category":null,"labels":{"edges":[{"node":{"name":"更多","color":"25B472"}},{"node":{"name":"命令行工具","color":"e05879"}},{"node":{"name":"tomnomnom","color":"54cc27"}}]},"comments":{"edges":[]}}},"pageContext":{"number":213,"previous":{"title":"gphper/grm: Golang 开发的 Redis 可视化工具，部署简单便捷，SSH连接，用户校验，操作日志、命令行模式、LUA 脚本执行、Redis 监控等","number":212},"next":{"title":"snowdreamtech/gserver: 使用 gin 和 golang 构建的简单静态 HTTP 服务器。跨平台，零配置","number":214}}}, "staticQueryHashes": ["151096407","2861350382"]}