Last active
May 14, 2024 23:13
-
-
Save kristopherjohnson/5065599 to your computer and use it in GitHub Desktop.
Read JSON from standard input and writes formatted JSON to standard output. Requires Node.js.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/usr/bin/env node | |
// Reads JSON from stdin and writes equivalent | |
// nicely-formatted JSON to stdout. | |
var stdin = process.stdin, | |
stdout = process.stdout, | |
inputChunks = []; | |
stdin.resume(); | |
stdin.setEncoding('utf8'); | |
stdin.on('data', function (chunk) { | |
inputChunks.push(chunk); | |
}); | |
stdin.on('end', function () { | |
var inputJSON = inputChunks.join(), | |
parsedData = JSON.parse(inputJSON), | |
outputJSON = JSON.stringify(parsedData, null, ' '); | |
stdout.write(outputJSON); | |
stdout.write('\n'); | |
}); |
Thanks for gist 💪.
Here's a terser version that uses some of the included fixes:
let inputJson = ''
process.stdin.setEncoding('utf8')
process.stdin.on('data', function (chunk) {
inputJson += chunk
})
process.stdin.on('end', function () {
const parsedData = JSON.parse(inputJson)
process.stdout.write(JSON.stringify(parsedData))
})
Yet another updated and terser version, ready to edit and run!
function readStdin() {
return new Promise(resolve => {
let buf = ''
process.stdin.setEncoding('utf8')
process.stdin.on('data', chunk => (buf += chunk))
process.stdin.on('end', () => resolve(buf))
})
}
async function main() {
const d = JSON.parse(await readStdin())
// do stuff with d, then...
console.log(JSON.stringify(d, null, 2))
}
Here's a oneliner that does the same thing (at least in mac and linux land, not sure about windows):
node -p 'JSON.stringify(JSON.parse(fs.readFileSync(0)),null,2)'
notably, JSON.parse
can work off of a buffer and fs.readFileSync(0)
reads the zero file descriptor, which is standard input.
Then, node -p
is a way to execute and log the output from a statement. You could also write it with a node -e 'console.log(...)'
if you would rather be in control of when or how the logging happens.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
'is what i am saying