Surface Error class constructors

[SReject]

The error instances should be surfaced/exposed so that when an error occurs, handling logic can differ between errors

// ... load db
try {
  await db.push("/test1","super test");
  // something else that raises its own DatabaseError instance unrelated to node-json-db
} catch (err) {

  // This is the current way to deduce error but is prone to false positives if the error wasn't given
  if (err.constructor.name === 'DatabaseError') {
    // ...
  }
}

Where as if Error classes are exposed, the check is less prone to false positives

import { DatabaseError as JsonDatabaseError/*, ... */ } from 'node-json-db';
// ... load db
try {
  await db.push("/test1","super test");
  // something else that raises its own DatabaseError instance unrelated to node-json-db
} catch (err) {
  if (err instanceof JsonDatabaseError) {
    // ...
  }
}

[Belphemur]

That would be a great QoL improvement.

You can open an MR for it akin to this:
#462

I'll accept it and merge it :)

[github-actions]

🎉 This issue has been resolved in version 2.1.2 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀