Process completed with exit code 1.

TypeError: useWallet is not a function ❯ tests/unit/use_wallet.spec.js:16:28

TypeError: useWallet is not a function ❯ tests/unit/use_wallet.spec.js:16:28

TypeError: useWallet is not a function ❯ tests/unit/use_wallet.spec.js:16:28

TypeError: useWallet is not a function ❯ tests/unit/use_wallet.spec.js:16:28

TypeError: useWallet is not a function ❯ tests/unit/use_wallet.spec.js:16:28

AssertionError: expected undefined to be 'test1' // Object.is equality - Expected: "test1" + Received: undefined ❯ tests/unit/database.spec.js:214:52

AssertionError: promise resolved "undefined" instead of rejecting - Expected: [Error: rejected promise] + Received: undefined ❯ tests/unit/database.spec.js:182:45

AssertionError: expected null to strictly equal Account{ publicKey: 'test1', …(8) } - Expected: Account { "coldAddress": "very cold", "contacts": Array [], "encExtsk": "", "encWif": "", "isHardware": false, "localProposals": Array [], "name": "", "publicKey": "test1", "shieldData": "", } + Received: null ❯ tests/unit/database.spec.js:32:39

AssertionError: promise resolved "undefined" instead of rejecting - Expected + Received - [Error: rejected promise] + undefined ❯ tests/unit/database.spec.js:182:45 This error originated in "tests/unit/database.spec.js" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "throws when called with an invalid account". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

'getEventEmitter' is defined but never used

'storeToRefs' is defined but never used