1.0.1+15

• Feat: Upgraded surrealdb.wasm to 1.0.1.

1.0.0-beta.22+14

• Feat: Upgraded surrealdb.wasm to 1.0.0-beta.22.
• Feat: Upgraded surrealdb_js to 1.0.1+7.
• Feat: Removed SurrealWasmMutex class as the issue #87 is likely resolved by PR #107.

1.0.0-beta.16+13

• Feat: Added mutex flag that default to false (off) to methods of the SurrealWasmMutex class to allow turn on/off the mutex locking mechanism.

1.0.0-beta.16+12

• Feat: Added SurrealWasmMutex class to workaround the issue #87 of the surrealdb.wasm.

1.0.0-beta.16+11

• Feat: Upgraded surrealdb.wasm to 1.0.0-beta.16.
• Feat: Upgraded surrealdb_js to 1.0.0-beta.20+4.

1.0.0-beta.14+9

• Feat: Added SurrealWasm.getInstance() to simplify instantiation of the Surreal class with the WasmEngine.

1.0.0-beta.14+8

• Feat: Upgraded surrealdb.wasm to 1.0.0-beta.14.
• Feat: Integrated with surrealdb_js 1.0.0-beta.14+3 that provide an unified API.

1.0.0-beta.14+10

• Feat: Changed SurrealWasm from extension to regular class.

0.9.0+7

• Feat: Upgraded to surrealdb.wasm 0.9.0, the official release of wasm module of the surrealdb 1.3.0.
• Feat: API breaking changes:
  • db.select() and db.query() that return single result, no longer requiring casting to List and retrieval by .first.
• Fix: Catched the error Encountered a non-object value in array within the library, preventing it from being exposed to the user. Reported the bug at surrealdb.wasm#56.

0.8.0+5

• Upgraded to official surrealdb.wasm 0.8.0 released for surrealdb 1.2.0.
• API breaking changes:
  • Previous: db.use(ns: 'test', db: 'test');
  • Current: db.use(namespace: 'test', database: 'test');