This is a build of jq, the command-line JSON processor in Javascript using Emscripten along with a wrapper for making it usable as a library.
It runs in the browser.
npm install jq-web
var jq = require('jq-web')
jq({
a: {
big: {
json: [
'full',
'of',
'important',
'things'
]
}
}
}, '.a.big.json | ["empty", .[1], "useless", .[3]] | join(" ")')the code above returns the string "empty of useless things".
There's a WASM version available at jq.wasm[.min].js, it is much faster.
If the target browser supports WebAssembly you can just include it normally. It will automatically look for the binary code at ./jq.wasm.wasm, so make sure it is available.
You can also import it with browserify require('jq-web/jq.wasm.js') if you want.
If you can't use WebAssembly, there's a better way to use the asm.js version.
By default, requiring jq-web will give you the ./jq.bundle.min.js file, which comes bundled with the static memory initialization inside the JS code. That's inefficient. For better performance and load sizes, require jq-web/jq[.min].js instead, and copy node_modules/jq-web/jq.js.mem to the directory you're serving the app from, as it will be loaded asynchronously in the runtime by the library.
The Emscripten runtime will try to require the fs module, and if it fails it will resort to an in-memory filesystem (almost no use of that is made by the library, but it is needed somehow). In Browserify there's a default {} that corresponds to the fs module, but in Webpack you must declare it as an empty module.
jq(<object>, <filter>) <object> will take a Javascript object, or scalar, whatever, and dump it to JSON, then it will return whatever your filter outputs and try to convert that into a JS object.
jq.raw(<json-string>, <filter>) <raw-output> will take a string that will be passed as it is to jq (like if you were doing echo '<json-string>' | jq <filter> on the command line) then return a string with the raw STDOUT response.
cat Makefile | head -n 10
# read it.
# then:
make
