fiatjaf_
The `return` is there to guarantee we don't run the initialization function twice. But why would this initialization change the URL of the page? Maybe what's happening is that when...
Chrome is stupid. I also don't know. It's something related to some permission asked for but not used. Must find some time to republish it.
Although it is already possible to call jq with arguments (I just don't document it because it doesn't work for most arguments) I believe your case will be nicely served...
Have you tried this? ```diff function getJq(jsonInput, filter = '.') { - return jq(JSON.parse(jsonInput), filter); + return jq.raw(jsonInput, filter); } ```
Actually, since your case doesn't need synchronous application of the function, you should use `jq.promised.raw().then(...)` instead, to prevent stupid errors.
Oops, I don't know how to proceed here.
Oh, you mean once you pass a flag it keeps being applied to next calls?
This is very odd. I took a look at it but can't see where the error is. Maybe we need an Emscripten specialist.
Wow, I guess we've found our Emscripten specialist! I have no idea of how to do that. It would be great if you could open a pull request.
Do you know how to fix it? Just calling `FS.close` on these streams?