Skip to content

Releases: fiatjaf/jq-web

v0.6.1

13 Feb 17:47
Compare
Choose a tag to compare
tag v0.6.1

0.6.0

04 Nov 11:05
Compare
Choose a tag to compare

@yurenchen000, @FGasper and @vvollers have fixed and updated all the things.

Now a single interface is supported -- a promise that resolves to a usable jq object. asm.js support was removed, everybody has to just use wasm.

0.5.1

03 Nov 01:58
Compare
Choose a tag to compare
  • Errors thrown by jq calls now return the full jq error output at the err.stack field.
  • Update Emscripten build (files are smaller and hopefully more performant).

0.5.0

13 Aug 13:50
Compare
Choose a tag to compare

Update jq to version 1.6.

0.4.1

12 Oct 18:38
Compare
Choose a tag to compare

Compiled files names have changed slightly.

0.4.0

12 Oct 10:58
Compare
Choose a tag to compare

Changed API: no more jq() calls, now we must use either jq.json() or jq.raw(), the same applies for jq.promised.json()/jq.promised.raw().

0.3.3

27 Apr 04:57
Compare
Choose a tag to compare

Fixed promised API once and for all (I hope).

0.3.1

26 Apr 20:01
Compare
Choose a tag to compare

Now the API has, in addition to jq() and jq.raw(),

  • jq.onInitialized.addListener()
  • jq.promised()
  • jq.promised.raw()

0.3.0

26 Apr 14:58
Compare
Choose a tag to compare

Now you don't get errors for calling jq() before the wasm or mem files finish loading. Instead, you'll get a default {} returned. Call it again after the initial loads to get correct values.

0.2.1

14 Feb 00:24
Compare
Choose a tag to compare
some optimizations and a non-memory-bundled version.